From: Andreas Schwab <schwab@linux-m68k.org>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Sergey Sharybin <sergey.vfx@gmail.com>,
Konstantin Khomoutov <flatworm@users.sourceforge.net>,
Git List <git@vger.kernel.org>
Subject: Re: git:// protocol over SSL/TLS
Date: Fri, 27 Dec 2013 15:29:59 +0100 [thread overview]
Message-ID: <87ioua4ba0.fsf@igel.home> (raw)
In-Reply-To: <vpqwqiqpe80.fsf@anie.imag.fr> (Matthieu Moy's message of "Fri, 27 Dec 2013 15:20:47 +0100")
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> You can verify integrity after the fact, but not guarantee
> confidentiality ... so it again depends on the definition of "security".
Since the OP is talking about anonymous access there is no need for
confidentiality in this case.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-12-27 14:30 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
2013-12-28 20:52 ` Sergey Sharybin
2013-12-28 0:11 ` brian m. carlson
2013-12-27 14:29 ` Andreas Schwab [this message]
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=87ioua4ba0.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=flatworm@users.sourceforge.net \
--cc=git@vger.kernel.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 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.