From: Jeff King <peff@peff.net>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] MaintNotes: use https:// instead of git:// when possible
Date: Tue, 1 Dec 2020 06:54:12 -0500 [thread overview]
Message-ID: <X8Yu5CephK3uvMeV@coredump.intra.peff.net> (raw)
In-Reply-To: <20201201095815.12850-1-avarab@gmail.com>
On Tue, Dec 01, 2020 at 10:58:15AM +0100, Ævar Arnfjörð Bjarmason wrote:
> Change advertised git:// links to https://. These all work as
> arguments to "git clone", but in addition they also have friendly web
> interfaces.
This is a good idea, I think. Not only for that reason, but because
https:// is more secure. You can verify tags from the maintainer's
signature, of course, but if you are just fetching some refs, you are
relying on the remote server not to lie to you. With https://, you at
least have some assurance that it is the remote server you intended to
talk to, and not a man-in-the-middle over the totally unauthenticated
git:// protocol.
> This leaves just git://ozlabs.org/~paulus/gitk as the only git://
> URL. As far as I can tell there's no web interface for it. There is
> e.g. https://git.ozlabs.org/?p=ppp.git which is a frontend for
> git://git.ozlabs.org/~paulus/ppp.git, but even though cloning the repo
> at git://git.ozlabs.org/~paulus/gitk.git works (not the "git" subdomain)
s/not/note/ in this last line?
-Peff
next prev parent reply other threads:[~2020-12-01 11:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 5:15 What's cooking in git.git (Nov 2020, #06; Mon, 30) Junio C Hamano
2020-12-01 9:46 ` [PATCH] cook: add github.com/git-vcs/git as a URL Ævar Arnfjörð Bjarmason
2020-12-01 9:58 ` [PATCH] MaintNotes: use https:// instead of git:// when possible Ævar Arnfjörð Bjarmason
2020-12-01 11:54 ` Jeff King [this message]
2020-12-01 19:07 ` Junio C Hamano
2020-12-02 1:43 ` Jeff King
2020-12-01 11:47 ` [PATCH] cook: add github.com/git-vcs/git as a URL Jeff King
2020-12-01 19:10 ` Junio C Hamano
2020-12-02 1:44 ` Jeff King
2020-12-01 18:57 ` Junio C Hamano
2020-12-02 4:33 ` What's cooking in git.git (Nov 2020, #06; Mon, 30) Felipe Contreras
2020-12-02 13:22 ` ds/config-literal-value (was Re: What's cooking in git.git (Nov 2020, #06; Mon, 30)) Derrick Stolee
2020-12-02 22:14 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X8Yu5CephK3uvMeV@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).