From: Eric Wong <e@80x24.org>
To: Jonny Grant <jg@jguk.org>
Cc: git@vger.kernel.org
Subject: Re: git:// warn as connection not secure
Date: Fri, 1 Dec 2023 21:24:23 +0000 [thread overview]
Message-ID: <20231201212423.M738201@dcvr> (raw)
In-Reply-To: <b6e0f49a-34ff-4e8e-9c3e-b8fd41d59f68@jguk.org>
Jonny Grant <jg@jguk.org> wrote:
> Hello
> May I ask if anyone has suggested adding a default warning that git:// is not a secure connection?
>
> ie "warning: git:// is not a secure connection. https and ssh are secure."
To be accurate, that would need an exclusion list of hosts behind
already-encrypted and trusted networks. So stuff like .onion hostnames
for Tor, and a user-configurable list of hosts in a private LAN/VPN.
next prev parent reply other threads:[~2023-12-01 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 11:57 git:// warn as connection not secure Jonny Grant
2023-12-01 21:24 ` Eric Wong [this message]
2023-12-05 20:42 ` Jonny Grant
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=20231201212423.M738201@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=jg@jguk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.