All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Justin Stitt <justinstitt@google.com>,
	"Kernel.org Tools" <tools@linux.kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH b4] b4: fix from header not using real name
Date: Thu, 27 Jul 2023 16:20:05 -0700	[thread overview]
Message-ID: <A250134A-7A60-47EB-8849-DB39D08B223B@kernel.org> (raw)
In-Reply-To: <20230727-fix-from-header-v1-1-2fb23c0a5da9@google.com>

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



-- 
Kees Cook

  parent reply	other threads:[~2023-07-27 23:20 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 [this message]
2023-08-01 16:12   ` Nick Desaulniers
2023-08-01 16:44     ` Kees Cook
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=A250134A-7A60-47EB-8849-DB39D08B223B@kernel.org \
    --to=kees@kernel.org \
    --cc=justinstitt@google.com \
    --cc=keescook@chromium.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 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.