From: David Woodhouse <dwmw2@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: Michal Marek <mmarek@suse.cz>,
torvalds@linux-foundation.org, aricart@memnix.com,
linux-kernel@vger.kernel.org, sedat.dilek@gmail.com,
keyrings@linux-nfs.org, rusty@rustcorp.com.au,
linux-security-module@vger.kernel.org, james.l.morris@oracle.com
Subject: Re: [PATCH 1/3] X.509: Fix certificate gathering again
Date: Thu, 28 May 2015 11:05:32 +0100 [thread overview]
Message-ID: <1432807532.3499.31.camel@infradead.org> (raw)
In-Reply-To: <32482.1432807089@warthog.procyon.org.uk>
On Thu, 2015-05-28 at 10:58 +0100, David Howells wrote:
> David Woodhouse <dwmw2@infradead.org> wrote:
>
> > > The only issue is that the makefile expressions are a bit hairy. For
> > > starters, we already have definitions for $(quote) and $(space) in
> > > kbuild. I'll have a closer look at the config_filename macro and try to
> > > simplify it somehow. But it's just cosmetics, the patch can be merged as
> > > is for now.
> >
> > I've actually changed my mind about the 'awk | base64 -d' bit. The error
> > handling is too poor. I'd like to do that in C with a variant of the
> > existing extract_cert tool, and make sure we have proper X.509
> > certificates and error handling/reporting.
>
> You could also do it in perl pretty easily.
It's a fairly trivial change to scripts/extract-cert.c though, which
gives you validation of the cert ASN.1 instead of just base64-decoding
and importing arbitrary crap as long as it's found between
-----BEGIN CERTIFICATE-----
and
-----END CERTIFICATE-----
Yeah, we could do the X.509 parsing/validation in perl too. But let's
not.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
prev parent reply other threads:[~2015-05-28 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18832.1432044859.1@warthog.procyon.org.uk>
2015-05-20 1:08 ` Michal Marek
2015-05-20 1:08 ` [PATCH 2/3] MODSIGN: Use filechk to generate .x509.list Michal Marek
2015-05-20 1:08 ` [PATCH 3/3] MODSIGN: Split user-supplied and autogenerated signing key Michal Marek
2015-05-26 16:15 ` [PATCH 1/3] X.509: Fix certificate gathering again David Howells
2015-05-26 19:49 ` Petko Manolov
2015-05-26 21:56 ` David Howells
2015-05-28 5:18 ` Michal Marek
2015-05-28 8:33 ` David Woodhouse
2015-05-28 9:58 ` David Howells
2015-05-28 10:05 ` David Woodhouse [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=1432807532.3499.31.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=aricart@memnix.com \
--cc=dhowells@redhat.com \
--cc=james.l.morris@oracle.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rusty@rustcorp.com.au \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.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
Powered by JetHome