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

Re: git format-patch --in-reply-to allows header injection. Intended?

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 4, 2014, 23:59 UTC
Message-ID
<xmqqd2bbq6mi.fsf@gitster.dls.corp.google.com>
In-Reply-To
<5408DCC5.8000607@nh2.me>
Niklas Hambüchen <mail@nh2.me> writes:
Show 8 quoted lines
> On 04/09/14 23:36, Junio C Hamano wrote:
>> While I do not think of a reason to specify such a string to the
>> in-reply-to option (I'd rather edit the output in the editor if I
>> wanted to do anything fancy [*1*]), I do not think there is a reason
>> why you want to add a code to forbid such use, either.
>
> My question was to find out whether I can pass untrusted user input to
> ...

Ah, in general, anybody who passes unvetted user input to any Git Porcelain deserves what s/he gets, so perhaps you would want to at least make sure that the input is a single line, or something.

Previous: Niklas Hambüchen
Message 4 of 4 in “git format-patch --in-reply-to allows header injection. Intended?”
  1. Niklas HambüchenSep 4, 2014
  2. Junio C HamanoSep 4, 2014
  3. Niklas HambüchenSep 4, 2014
  4. Junio C HamanoSep 4, 2014

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.