From: Jarkko Sakkinen <jarkko@kernel.org>
To: Andrew Zaborowski <andrew.zaborowski@intel.com>
Cc: keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH v2] keys: X.509 public key issuer lookup without AKID
Date: Thu, 21 Jan 2021 17:22:57 +0200 [thread overview]
Message-ID: <YAmcURxlfK8TM5Kj@kernel.org> (raw)
In-Reply-To: <CAOq732KJMWRED1Zz3ZR-7=KAJMKGseKA2r0a97prNFCbB1K+DQ@mail.gmail.com>
On Thu, Jan 21, 2021 at 12:31:59PM +0100, Andrew Zaborowski wrote:
> On Wed, 20 Jan 2021 at 02:57, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> > On Fri, Jan 15, 2021 at 11:40:18AM +0100, Andrew Zaborowski wrote:
> > > Note: asymmetric_match_key_ids can be used as part of a generic key
> > > API query, or as part of a find_asymmetric_key call (only used in
> > > crypto/asymmetric_keys/ for trust verification and similar) but
> > > find_asymmetric_key will then perform an extra check. In any case
> > > without more background I think it's preferable to minimize the
> > > matching logic changes, and even assuming that the logic could be
> > > improved it may be best to keep it as is because existing tools may
> > > rely on it.
> >
> > You could give a couple of usage examples, by using this cert
> >
> > https://letsencrypt.org/docs/certificates-for-localhost/
> >
> > That is good information to store in the commit log for future and
> > also works as a tested-by criteria.
>
> Ok, resending the patch rebased on top of the BUG_ON fix (applied
> locally) and adding the command line example.
>
> Best regards
Please make it a patch set then. Locally applied patches do not
count.
/Jarkko
prev parent reply other threads:[~2021-01-21 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 20:40 [PATCH v2] keys: X.509 public key issuer lookup without AKID Andrew Zaborowski
2021-01-15 8:19 ` Jarkko Sakkinen
2021-01-15 8:21 ` Jarkko Sakkinen
2021-01-15 10:40 ` Andrew Zaborowski
2021-01-15 10:44 ` Andrew Zaborowski
2021-01-20 1:54 ` Jarkko Sakkinen
2021-01-21 11:31 ` Andrew Zaborowski
2021-01-21 15:22 ` Jarkko Sakkinen [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=YAmcURxlfK8TM5Kj@kernel.org \
--to=jarkko@kernel.org \
--cc=andrew.zaborowski@intel.com \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.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.