From: Kees Cook <keescook@chromium.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Kees Cook <kees@kernel.org>,
Justin Stitt <justinstitt@google.com>,
"Kernel.org Tools" <tools@linux.kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH b4] b4: fix from header not using real name
Date: Tue, 1 Aug 2023 09:44:54 -0700 [thread overview]
Message-ID: <202308010939.9EC4C98@keescook> (raw)
In-Reply-To: <CAKwvOdn0ePdAfQBby9zaXi7CA64Foc2NRJfzYyQHaOhz2C9+VA@mail.gmail.com>
On Tue, Aug 01, 2023 at 09:12:35AM -0700, Nick Desaulniers wrote:
> On Thu, Jul 27, 2023 at 4:20 PM Kees Cook <kees@kernel.org> wrote:
> >
> > On July 27, 2023 11:47:36 AM PDT, Justin Stitt <justinstitt@google.com> wrote:
> > >When using `b4 send` there seems to be an issue with the real name not
> > >being included in the From: header.
> > >
> > >Here's an example:
> > >| From: justinstitt@google.com
> > >
> > >Whereas, something like the following is preferred:
> > >| From: Justin Stitt <justinstitt@google.com>
> >
> > Hmm. There are actually two "From" fields. There's envelope sender "From" (which is what -f sets), and the in-body "From:" field. I wonder if b4 isn't constructing the in-body From: field, and when missing, the MUAs add it based on the -f flag?
> >
> > >This patch fixes this issue and achieves the preferred behavior (above)
> > >by properly using both parts of a user's `from` field from their config.
> > >
> > >A .gitconfig like this now properly works
> > >| [sendemail]
> > >| from = Justin Stitt <justinstitt@google.com>
> >
> > Perhaps what's needed is this (which is what I've been using forever):
> >
> > [sendemail]
> > envelopesender = auto
>
> Thanks for the tip; I'll give that a shot. Do you have `from` set
> under `[sendemail]` as well or no?
I don't, no. I also don't use "b4 send" (just "git send-email"), so it's
not clear to me what's actually going wrong here. It still looks to me
like either "b4 send" isn't writing a "From:" header, or Justin (and
your?) MUA is removing/replacing it when it processes the "-f" argument.
FWIW, my MUA is postfix. (Though actually, I guess, it's the MTA, b4 or
git is the MUA... whatever. The thing I hand off to is postfix.)
For the relevant ~/.gitconfig settings, I have:
[user]
email = keescook@chromium.org
name = Kees Cook
[sendemail]
envelopesender = auto
confirm = auto
--
Kees Cook
next prev parent reply other threads:[~2023-08-01 16:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 18:47 [PATCH b4] b4: fix from header not using real name Justin Stitt
2023-07-27 23:07 ` Justin Stitt
2023-07-27 23:20 ` Kees Cook
2023-08-01 16:12 ` Nick Desaulniers
2023-08-01 16:44 ` Kees Cook [this message]
2023-08-01 17:04 ` Konstantin Ryabitsev
2023-08-01 20:07 ` Justin Stitt
2023-08-01 22:25 ` Nick Desaulniers
2023-08-01 22:27 ` Justin Stitt
2023-08-01 22:34 ` Nick Desaulniers
2023-08-03 17:47 ` Nick Desaulniers
2023-08-03 17:51 ` Justin Stitt
2023-08-03 18:17 ` Konstantin Ryabitsev
2023-08-03 18:41 ` Nick Desaulniers
2023-08-03 19:32 ` Konstantin Ryabitsev
2023-08-03 20:58 ` Nick Desaulniers
2023-08-03 18:41 ` Justin Stitt
2023-08-01 22:20 ` Nick Desaulniers
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=202308010939.9EC4C98@keescook \
--to=keescook@chromium.org \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=ndesaulniers@google.com \
--cc=tools@linux.kernel.org \
/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