git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] documentation: add git transport security notice

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 24, 2013, 22:28 UTC
Message-ID
<7vy59z5ej9.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130624215733.GU2457@bacardi.hollandpark.frase.id.au>
Fraser Tweedale <frase@frase.id.au> writes:
Show 6 quoted lines
> Junio, do you prefer the following more generic wording?  If so I
> will re-roll the patch (also note s/protocol/transport/ which is
> more appropriate, I think).
>
>  The git transport is insecure and should be used with caution on
>  unsecured networks.

Generic but I somehow find it overly vague (it is unclear what kind of "insecure-ness" it is talking about).

  Because the git transport does not do any authentication, it
  should be used with caution on unsecured networks.
Perhaps?
Previous: Fredrik Gustafsson
Message 7 of 7 in “documentation: add git transport security notice”
  1. documentation: add git transport security noticeFraser Tweedale, Jun 24, 2013
  2. Junio C HamanoJun 24, 2013
  3. Fraser TweedaleJun 24, 2013
  4. Fredrik GustafssonJun 24, 2013
  5. Junio C HamanoJun 24, 2013
  6. Fredrik GustafssonJun 24, 2013
  7. Junio C HamanoJun 24, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.