From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: tools@linux.kernel.org
Subject: Re: [PATCH] validate: Use patatt's configured keyring as fallback
Date: Thu, 7 Oct 2021 13:41:57 -0400 [thread overview]
Message-ID: <163362850160.581076.8811630052019728688.b4-ty@linuxfoundation.org> (raw)
In-Reply-To: <20211007165551.2312946-1-keescook@chromium.org>
On Thu, 7 Oct 2021 09:55:51 -0700, Kees Cook wrote:
> If b4 doesn't have an explicit keyringsrc configured, attempt to fetch
> it from patatt configuration instead. This avoids some very confusing
> situations where patatt would validate and b4 would reject. (I had an
> expired pubkey in my gpg default keyring, but the same pubkey had an
> updated expiration date in patatt's keyring.)
>
>
> [...]
Applied, thanks!
[1/1] validate: Use patatt's configured keyring as fallback
commit: 3847a92a365a96270ab0de6111f349e98379f930
Best regards,
--
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
prev parent reply other threads:[~2021-10-07 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 16:55 [PATCH] validate: Use patatt's configured keyring as fallback Kees Cook
2021-10-07 17:41 ` Konstantin Ryabitsev [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=163362850160.581076.8811630052019728688.b4-ty@linuxfoundation.org \
--to=konstantin@linuxfoundation.org \
--cc=keescook@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).