From: Michal Marek <mmarek@suse.cz>
To: David Howells <dhowells@redhat.com>
Cc: 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,
dwmw2@infradead.org
Subject: Re: [PATCH 1/3] X.509: Fix certificate gathering again
Date: Thu, 28 May 2015 13:18:52 +0800 [thread overview]
Message-ID: <5566A53C.6020309@suse.cz> (raw)
In-Reply-To: <19779.1432656938@warthog.procyon.org.uk>
Dne 27.5.2015 v 00:15 David Howells napsal(a):
> Hi Michal,
>
> Could you have a look at the patch at the end of my branch:
>
> http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=modsign-pkcs7
>
> It changes things from picking up arbitrary *.x509 files dropped in the kernel
> source and/or build directory to taking a single named PEM file with all the
> additional certs as a string config option. The PEM file can contain multiple
> certs simply cat'd together.
>
> If you're okay with that, it obsoletes these patches of yours.
I'm fine with the concept as it indeed solves the problem with the
wildcard matching for good. So please drop the patches that I posted.
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.
Michal
next prev parent reply other threads:[~2015-05-28 5:19 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 ` [PATCH 1/3] X.509: Fix certificate gathering again 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 [this message]
2015-05-28 8:33 ` David Woodhouse
2015-05-28 9:58 ` David Howells
2015-05-28 10:05 ` David Woodhouse
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=5566A53C.6020309@suse.cz \
--to=mmarek@suse.cz \
--cc=aricart@memnix.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--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=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