From: Jonathan Nieder <jrnieder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, Joey Hess <joeyh@joeyh.name>,
git@vger.kernel.org
Subject: Re: [PATCH] avoid insecure use of mail in man page example
Date: Sun, 17 Oct 2021 17:55:05 -0700 [thread overview]
Message-ID: <YWzF6deqfffBM7ub@gmail.com> (raw)
In-Reply-To: <YVOy0HLvManYQdGo@coredump.intra.peff.net>
Hi,
Jeff King wrote:
> On Tue, Sep 28, 2021 at 04:46:52PM -0700, Junio C Hamano wrote:
>>> On Tue, Sep 28, 2021 at 08:16:48AM -0400, Joey Hess wrote:
>>>> As recently seen in fail2ban's security hole (CVE-2021-32749),
>>>> piping user controlled input to mail is exploitable,
>>>> since a line starting with "~! foo" in the input will run command foo.
[...]
>> It is not the primary focus for this documentation page to teach how
>> to send e-mails in the first place. Instead of risking confused
>> users rightly complain with "my 'mail' does not understand the -E
>> option---what does this do?", I wonder if it is better to just change it to
>>
>> git rev-list --pretty ...
>> - fi |
>> - mail -s ...
>> + fi >>/var/log/update.log
>>
>> so that it illustrates what's available *out* *of* *us* to the
>> authors of the script, without having to teach them "mail" and other
>> things we are responsible for.
>
> Yeah, I'd agree that side-stepping the issue entirely is a good
> direction. Doing it right is probably best left to tools like
> git-multimail.
This makes sense to me. Joey, are you planning to send an updated
version of the patch, or would you like us to take care of it?
Thanks,
Jonathan
prev parent reply other threads:[~2021-10-18 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 12:16 [PATCH] avoid insecure use of mail in man page example Joey Hess
2021-09-28 18:46 ` Jeff King
2021-09-28 23:46 ` Junio C Hamano
2021-09-29 0:26 ` Jeff King
2021-10-18 0:55 ` Jonathan Nieder [this message]
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=YWzF6deqfffBM7ub@gmail.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joeyh@joeyh.name \
--cc=peff@peff.net \
/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).