All of lore.kernel.org
 help / color / mirror / Atom feed
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][RESEND#15] keys: Handle missing Authority Key Identifier X509 extension
Date: Thu, 14 Jan 2021 05:19:47 +0200	[thread overview]
Message-ID: <X/+4U/rAyi+g0sRQ@kernel.org> (raw)
In-Reply-To: <CAOq732LXcYQ2TpqunHzL0ZYy77X=BAJOotTvh--zf=UD9qdCnw@mail.gmail.com>

On Wed, Jan 13, 2021 at 03:31:04PM +0100, Andrew Zaborowski wrote:
> On Tue, 12 Jan 2021 at 02:41, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> > On Mon, Jan 11, 2021 at 03:27:57PM +0100, Andrew Zaborowski wrote:
> > > On Sun, 10 Jan 2021 at 05:45, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> > > > I think that a more sane way to fix this issue, would be to add field
> > > > 'self_signed' to 'struct public_key_signature', and remove the
> > > > equivalent field from 'struct x509_certificate'.
> > >
> > > Ok, that's also an option.  I went for directly adding the
> > > cert->sig->auth_ids because the name ".auth_ids" only implies that it
> > > contains the signing authority's key IDs, which is something that we
> > > have and does exist in the input file.  The name doesn't imply that it
> > > should specifically be in the AKID extension.  Similarly
> > > x509_key_preparse even generates a key description even though a
> > > description is not part of the x509 format.
> > >
> > > >
> > > > Minor updates are required to:
> > > >
> > > > - x509_check_for_self_signed()
> > > > - pkcs7_verify_sig_chain()
> > > >
> > > > Then you can use then new field to refine the check in
> > > > restrict_link_by_signature().
> 
> I decided to try supporting key lookups without the AKID extension
> first, as I proposed in
> https://marc.info/?l=linux-keyrings&m=158621913606374&w=2 , because
> this would make the new sig->self_signed field obsolete.  It's a just
> slightly bigger change but fixes verification for a bigger set of
> certificates that are in use.
> 
> If there are arguments against it then I'm going to send a patch to
> add a sig->self_signed as you suggested.
> 
> Many thanks

OK, I'll check that one then. Thank you.

/Jarkko

      reply	other threads:[~2021-01-14  3:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 16:40 [PATCH][RESEND#15] keys: Handle missing Authority Key Identifier X509 extension Andrew Zaborowski
2021-01-04 16:40 ` [PATCH][RESEND] keys: Update comment for restrict_link_by_key_or_keyring_chain Andrew Zaborowski
2021-01-10  4:51   ` Jarkko Sakkinen
2021-01-10  4:45 ` [PATCH][RESEND#15] keys: Handle missing Authority Key Identifier X509 extension Jarkko Sakkinen
2021-01-11 14:27   ` Andrew Zaborowski
2021-01-12  1:40     ` Jarkko Sakkinen
2021-01-13 14:31       ` Andrew Zaborowski
2021-01-14  3:19         ` 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=X/+4U/rAyi+g0sRQ@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.