From: Michal Marek <mmarek@suse.cz>
To: David Howells <dhowells@redhat.com>, rusty@rustcorp.com.au
Cc: keyrings@linux-nfs.org, dmitry.kasatkin@gmail.com,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH 0/5] MODSIGN: Use PKCS#7 for module signatures [ver #3]
Date: Wed, 25 Feb 2015 14:16:03 +0100 [thread overview]
Message-ID: <54EDCB13.7030704@suse.cz> (raw)
In-Reply-To: <20150206145834.17303.59753.stgit@warthog.procyon.org.uk>
On 2015-02-06 15:58, David Howells wrote:
> Note that the revised sign-file program no longer supports the "-s <signature>"
> option as I'm not sure what the best way to deal with this is. Do we generate
> a PKCS#7 cert from the signature given, or do we get given a PKCS#7 cert? I
> lean towards the latter.
It would be convenient to have it, since pesign also has
--import-raw-signature. But it can be added back later.
Michal
prev parent reply other threads:[~2015-02-25 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 14:58 [PATCH 0/5] MODSIGN: Use PKCS#7 for module signatures [ver #3] David Howells
2015-02-06 14:58 ` [PATCH 1/5] X.509: Extract both parts of the AuthorityKeyIdentifier " David Howells
2015-02-06 14:58 ` [PATCH 2/5] X.509: Support X.509 lookup by Issuer+Serial form " David Howells
2015-02-06 14:59 ` [PATCH 3/5] PKCS#7: Allow detached data to be supplied for signature checking purposes " David Howells
2015-02-06 14:59 ` [PATCH 4/5] MODSIGN: Provide a utility to append a PKCS#7 signature to a module " David Howells
2015-02-25 13:18 ` Michal Marek
2015-05-01 13:26 ` David Howells
2015-02-06 14:59 ` [PATCH 5/5] MODSIGN: Use PKCS#7 messages as module signatures " David Howells
2015-02-25 13:16 ` Michal Marek [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=54EDCB13.7030704@suse.cz \
--to=mmarek@suse.cz \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.