mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Antony Vennard <antony@vennard.ch>, David Howells <dhowells@redhat.com>
Cc: keyrings@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] Load OpenSSL config if present in sign-file.c
Date: Fri, 03 Feb 2017 09:07:39 +0000	[thread overview]
Message-ID: <1486112858.4450.3.camel@infradead.org> (raw)
In-Reply-To: <20170203013118.14634-1-antony@vennard.ch>

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

On Fri, 2017-02-03 at 02:31 +0100, Antony Vennard wrote:
> sign-file documentation on kernel.org advertises the fact that 
> sign-file can use OpenSSL loadable engine support using pkcs#11 uri 
> syntax (rfc 7512) for loading private keys from hardware tokens, if 
> openssl loadable engine support is present.
> 
> Unfortunately, if openssl configuration files are not loaded there is 
> no way (to my knowledge) for openssl to load third party pkcs#11 
> libraries as specified by openssl configuration.

ENGINE_pkcs11 should be configured to load p11-kit-proxy.so as its
default provider module.

Any third party PKCS#11 module you want to use should be configured in
p11-kit properly, and it'll then be available to well-behaved
applications. Including sign-file.

You should need any of the special OpenSSL config horridness.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]

  parent reply	other threads:[~2017-02-03  9:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03  1:31 Antony Vennard
2017-02-03  1:31 ` [PATCH 1/1] " Antony Vennard
2017-02-03  9:07 ` David Woodhouse [this message]
2017-02-03  9:23   ` [PATCH 0/1] " Antony Vennard
2017-02-03  9:36     ` 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=1486112858.4450.3.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=antony@vennard.ch \
    --cc=dhowells@redhat.com \
    --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

all inboxes | Powered by JetHome®