public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 2/2] git-r3.eclass: Explicitly warn about unsecure protocols
Date: Wed, 23 Aug 2017 11:46:02 +0300	[thread overview]
Message-ID: <20170823114602.4b19ebe6b225f4a57af3448e@gentoo.org> (raw)
In-Reply-To: <20170819082502.27716-2-mgorny@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]

On Sat, 19 Aug 2017 10:25:02 +0200 Michał Górny wrote:
> Explicitly warn about any URI that uses an unsecure protocol (git, http)
> even if it's a fallback URI. This is necessary because an attacker may
> block HTTPS connections, effectively forcing the fallback to
> the unsecure protocol.
[...]
> +	local r
> +	for r in "${repos[@]}"; do
> +		if [[ ${r} == git:* || ${r} == http:* ]]; then
> +			ewarn "git-r3: ${r%%:*} protocol in unsafe and may be subject to MITM attacks"
> +			ewarn "(even if used only as fallback). Please use https instead."
> +			ewarn "[URI: ${r}]"
> +		fi
> +	done
> +

Sigh... https also makes MITM attacks possible, especially if SSL
or TLS < 1.2 is used or are allowed and protocol version downgrade
attack may be performed.

Such messages create a false impression of a safety of https.
Safety more or less can be gained by verifying GPG signatures and
fingerprints of the upstream commits, if upstream supports this. Of
course using https is better than using http or git, but better
only by a bit.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-08-23  8:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19  8:25 [gentoo-dev] [PATCH 1/2] git-r3.eclass: Update docs to discourage unsafe protocols Michał Górny
2017-08-19  8:25 ` [gentoo-dev] [PATCH 2/2] git-r3.eclass: Explicitly warn about unsecure protocols Michał Górny
2017-08-19 22:01   ` [gentoo-dev] " Duncan
2017-08-19 22:39     ` Michał Górny
2017-08-23  8:46   ` Andrew Savchenko [this message]
2017-08-25 13:51     ` [gentoo-dev] " Michał Górny
2017-09-03 18:00       ` Andrew Savchenko
2017-08-25 15:46     ` Hanno Böck
2017-09-03 18:08       ` Andrew Savchenko
2017-08-20 18:05 ` [gentoo-dev] [PATCH 1/2] git-r3.eclass: Update docs to discourage unsafe protocols William Hubbs
2017-08-20 19:25   ` Michał Górny
2017-08-25 13:52 ` Michał Górny

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=20170823114602.4b19ebe6b225f4a57af3448e@gentoo.org \
    --to=bircoph@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox