linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juerg Haefliger <juerg.haefliger@hpe.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org, keyrings@vger.kernel.org,
	dwmw2@infradead.org
Subject: Re: [PATCH v2] scripts/sign-file.c: Add support for signing with a raw signature
Date: Thu, 18 Feb 2016 10:26:16 +0100	[thread overview]
Message-ID: <56C58E38.4080502@hpe.com> (raw)
In-Reply-To: <56BB3A09.3080501@hpe.com>

On 02/10/2016 02:24 PM, Juerg Haefliger wrote:
> On 02/10/2016 11:12 AM, David Howells wrote:
>> Juerg Haefliger <juerg.haefliger@hpe.com> wrote:
>>
>>> This patch adds support for signing a kernel module with a raw
>>> detached PKCS#7 signature/message.
>>>
>>> The signature is not converted and is simply appended to the module so
>>> it needs to be in the right format. Using openssl, a valid signature can
>>> be generated like this:
>>>   $ openssl smime -sign -nocerts -noattr -binary -in <module> -inkey \
>>>     <key> -signer <x509> -outform der -out <raw sig>
>>>
>>> The resulting raw signature from the above command is (more or less)
>>> identical to the raw signature that sign-file itself can produce like
>>> this:
>>>   $ scripts/sign-file -d <hash algo> <key> <x509> <module>
>>
>> What's the usage case for this?  Can it be done instead with openssl PKCS#11?
> 
> Our internal signing service doesn't support PKCS#11. I have to submit the blobs
> and get detached PKCS#7 messages back. I don't claim I fully understand all the
> different signing mechanisms but everything worked just fine until support for
> signing with a detached signature was removed. IMO that's a regression, which
> I'm trying to fix with this patch.

Any comments?

Thanks
...Juerg

  reply	other threads:[~2016-02-18  9:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30  9:18 [PATCH] scripts/sign-file.c: Add support for signing with a raw signature Juerg Haefliger
2016-02-03 20:34 ` David Howells
2016-02-04  9:07   ` Juerg Haefliger
2016-02-04 10:42     ` David Howells
2016-02-03 20:45 ` David Howells
2016-02-04 11:09 ` [PATCH v2] " Juerg Haefliger
2016-02-09 16:44   ` David Howells
2016-02-10 10:12   ` David Howells
2016-02-10 10:25     ` David Woodhouse
2016-02-10 13:07     ` Juerg Haefliger
2016-02-10 13:24     ` Juerg Haefliger
2016-02-18  9:26       ` Juerg Haefliger [this message]
2016-02-18 17:23   ` David Howells

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=56C58E38.4080502@hpe.com \
    --to=juerg.haefliger@hpe.com \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).