From: James Morris <jmorris@namei.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>,
David Howells <dhowells@redhat.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Gary Hook <gary.hook@amd.com>,
"David S. Miller" <davem@davemloft.net>,
james.morris@microsoft.com, "Serge E. Hallyn" <serge@hallyn.com>,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2][RESEND] X.509: unpack RSA signatureValue field from BIT STRING
Date: Thu, 21 Jun 2018 11:44:29 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1806211144140.30225@namei.org> (raw)
In-Reply-To: <20180620143807.fo7c5endwd5yy24r@gondor.apana.org.au>
On Wed, 20 Jun 2018, Herbert Xu wrote:
> On Wed, Jun 20, 2018 at 02:24:54PM +0200, Maciej S. Szmigiero wrote:
> >
> > A friendly ping here.
> >
> > @AMD people:
> > Without this patch, in-kernel X.509 certificate verification is broken
> > on AMD CCP RSA implementation.
> >
> > For example, loading wireless regulatory database gives the following
> > errors:
> > > [ 21.310361] cfg80211: Problem loading in-kernel X.509 certificate (-22)
> > > [ 21.351717] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
> >
> > Kernel modules signature verification probably has similar problem, too.
> >
> > That's why it would be nice if you could ack this patch, please.
>
> David/James, is there an issue with the patch?
Not from my POV.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2018-06-21 1:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 12:23 [PATCH v2][RESEND] X.509: unpack RSA signatureValue field from BIT STRING Maciej S. Szmigiero
2018-06-02 19:12 ` Maciej S. Szmigiero
2018-06-20 12:24 ` Maciej S. Szmigiero
2018-06-20 14:38 ` Herbert Xu
2018-06-21 1:44 ` James Morris [this message]
2018-06-21 2:32 ` Herbert Xu
2018-06-21 6:45 ` James Morris
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=alpine.LRH.2.21.1806211144140.30225@namei.org \
--to=jmorris@namei.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=gary.hook@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=james.morris@microsoft.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
--cc=serge@hallyn.com \
--cc=thomas.lendacky@amd.com \
/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