Re: [PATCH 0/1] Load OpenSSL config if present in sign-file.c

2017-02-03 Thread David Woodhouse
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

Re: [PATCH 0/1] Load OpenSSL config if present in sign-file.c

2017-02-03 Thread Antony Vennard
On 03/02/17 10:07, David Woodhouse wrote: > 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 hardwar

Re: [PATCH 0/1] Load OpenSSL config if present in sign-file.c

2017-02-03 Thread David Woodhouse
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

[PATCH 0/1] Load OpenSSL config if present in sign-file.c

2017-02-02 Thread Antony Vennard
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 no