From: "Bernhard R. Link" <brl+git@mail.brlink.eu>
To: Sergey Sharybin <sergey.vfx@gmail.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Andreas Schwab <schwab@linux-m68k.org>,
Konstantin Khomoutov <flatworm@users.sourceforge.net>,
Git List <git@vger.kernel.org>
Subject: Re: git:// protocol over SSL/TLS
Date: Fri, 27 Dec 2013 17:26:07 +0100 [thread overview]
Message-ID: <20131227162606.GA6973@client.brlink.eu> (raw)
In-Reply-To: <CAErtv25URyB3znN1CMd87374NUjaSFvg=cee_-c=s8bB2j052A@mail.gmail.com>
* Sergey Sharybin <sergey.vfx@gmail.com> [131227 15:25]:
> Security in this case is about being sure everyone gets exactly the
> same repository as stored on the server, without any modifications to
> the sources cased by MITM.
Note that ssl (and thus https) only helps here against a resource-less
man-in-the-middle. Getting catch-all CA-signed certificates is said to
no longer available to everyone as easily as it was some years ago, but
unless you allow only one private CA (and even there clients often fail)
you still should assume everyone resourceful enough to still be able to
do MITM.
Bernhard R. Link
next prev parent reply other threads:[~2013-12-27 17:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 12:59 git:// protocol over SSL/TLS Sergey Sharybin
2013-12-27 13:29 ` Andreas Schwab
2013-12-27 13:36 ` Konstantin Khomoutov
2013-12-27 13:58 ` Sergey Sharybin
2013-12-27 14:12 ` Andreas Schwab
2013-12-27 14:16 ` Konstantin Khomoutov
2013-12-27 14:18 ` Sergey Sharybin
2013-12-27 14:20 ` Matthieu Moy
2013-12-27 14:25 ` Sergey Sharybin
2013-12-27 14:39 ` Konstantin Khomoutov
2013-12-27 14:47 ` Sergey Sharybin
2013-12-27 14:56 ` Konstantin Khomoutov
2013-12-28 9:37 ` Jeff King
2013-12-27 16:26 ` Bernhard R. Link [this message]
2013-12-28 20:52 ` Sergey Sharybin
2013-12-28 0:11 ` brian m. carlson
2013-12-27 14:29 ` Andreas Schwab
2013-12-27 14:21 ` Pyeron, Jason J CTR (US)
2013-12-27 14:14 ` Konstantin Khomoutov
2013-12-27 22:21 ` Junio C Hamano
2013-12-28 20:00 ` Ilari Liusvaara
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=20131227162606.GA6973@client.brlink.eu \
--to=brl+git@mail.brlink.eu \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=flatworm@users.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=sergey.vfx@gmail.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).