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:36:45 +0000 [thread overview]
Message-ID: <1486114605.4450.11.camel@infradead.org> (raw)
In-Reply-To: <eb178142-3e31-7d14-84d1-f376df45776d@vennard.ch>
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
On Fri, 2017-02-03 at 10:23 +0100, Antony Vennard wrote:
> On 03/02/17 10:07, David Woodhouse wrote:
> > You should[n't] need any of the special OpenSSL config horridness.
> Ah, I did not even know that was a thing. I do now. That looks like a
> much neater solution. Forget this patch then :)
As a general rule, this is true of *every* well-behaved application in
a Linux system.
If you have a PKCS#11 provider configured with a p11-kit .module file,
then it should automatically be usable just by providing a suitable
RFC7512 PKCS#11 URI in place of a filename.
If you find any application which can't do that on Fedora, file a bug
and Cc me. It's violating the packaging guidelines.
Other distributions may catch up in a decade or two (hey, I hear Debian
might even get coherent SSL trust settings by 2020...)
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]
prev parent reply other threads:[~2017-02-03 9:36 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 ` [PATCH 0/1] " David Woodhouse
2017-02-03 9:23 ` Antony Vennard
2017-02-03 9:36 ` 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=1486114605.4450.11.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®