Re: [openssl-dev] [RFC v2 2/2] pem: load engine keys

2016-12-06 Thread Richard Levitte
In message <1480697558.2410.33.ca...@hansenpartnership.com> on Fri, 02 Dec 2016 08:52:38 -0800, James Bottomley said: James.Bottomley> On Thu, 2016-12-01 at 09:30 +0100, Richard Levitte wrote: James.Bottomley> > James.Bottomley> > James Bottomley

Re: [openssl-dev] [RFC v2 2/2] pem: load engine keys

2016-12-06 Thread Richard Levitte
In message <1481042048.4406.14.ca...@hansenpartnership.com> on Tue, 06 Dec 2016 08:34:08 -0800, James Bottomley said: James.Bottomley> On Tue, 2016-12-06 at 15:12 +0100, Richard Levitte wrote: James.Bottomley> > In message

Re: [openssl-dev] [RFC v2 2/2] pem: load engine keys

2016-12-06 Thread James Bottomley
On Tue, 2016-12-06 at 17:47 +0100, Richard Levitte wrote: > In message <1481042048.4406.14.ca...@hansenpartnership.com> on Tue, > 06 Dec 2016 08:34:08 -0800, James Bottomley < > james.bottom...@hansenpartnership.com> said: > > James.Bottomley> On Tue, 2016-12-06 at 15:12 +0100, Richard Levitte >

Re: [openssl-dev] Building 1.1.0c for WIN32

2016-12-06 Thread Joel Winarske
ActiveState Perl64: "This is perl 5, version 24, subversion 0 (v5.24.0) built for MSWin32-x64-multi-thread" I sorted it out. The key is to build from either "VS2015 x86 Native Tools Command Prompt" || "VS2015 x64 Native Tools Command Prompt" It doesn't like being built from: "MSBuild Command

Re: [openssl-dev] [RFC v2 2/2] pem: load engine keys

2016-12-06 Thread Benjamin Kaduk
On 12/06/2016 11:01 AM, James Bottomley wrote: > The next problem is that this is slightly harder simply to insert into > the PEM code. The BIO parsing is done in PEM_bytes_read_bio() not > PEM_read_bio_PrivateKey(). The easy way to cope with this would be to > move PEM parsing into the

Re: [openssl-dev] [RFC v2 2/2] pem: load engine keys

2016-12-06 Thread Richard Levitte
In message <20161206.223057.237264374331072901.levi...@openssl.org> on Tue, 06 Dec 2016 22:30:57 +0100 (CET), Richard Levitte said: levitte> That being said, it should certainly be easy enough to change the levitte> appropriate places to make sure headers are available as

Re: [openssl-dev] Building 1.1.0c for WIN32

2016-12-06 Thread Benjamin Kaduk
On 12/05/2016 09:22 PM, Joel Winarske wrote: > Hi folks, > > I'm having trouble building 1.1.0c for WIN32. Perl ends up in a hard > loop. I see same symtom building 1.0.2j, but different error. Any > suggestions to get past this? > What version of perl? -Ben -- openssl-dev mailing list To

Re: [openssl-dev] [RFC v2 2/2] pem: load engine keys

2016-12-06 Thread James Bottomley
On Tue, 2016-12-06 at 15:12 +0100, Richard Levitte wrote: > In message <1480697558.2410.33.ca...@hansenpartnership.com> on Fri, > 02 Dec 2016 08:52:38 -0800, James Bottomley < > james.bottom...@hansenpartnership.com> said: > > James.Bottomley> On Thu, 2016-12-01 at 09:30 +0100, Richard Levitte >

Re: [openssl-dev] [RFC v2 2/2] pem: load engine keys

2016-12-06 Thread Richard Levitte
In message <58472e4f.3010...@roumenpetrov.info> on Tue, 06 Dec 2016 23:31:59 +0200, Roumen Petrov said: openssl> Hi Richard, openssl> openssl> Richard Levitte wrote: openssl> > [SNIP] openssl> > James.Bottomley> 1. We agreed that usability is greatly enhanced if

Re: [openssl-dev] [RFC v2 2/2] pem: load engine keys

2016-12-06 Thread Richard Levitte
In message <1481043672.4406.22.ca...@hansenpartnership.com> on Tue, 06 Dec 2016 09:01:12 -0800, James Bottomley said: James.Bottomley> On Tue, 2016-12-06 at 17:47 +0100, Richard Levitte wrote: James.Bottomley> > In message

Re: [openssl-dev] [RFC v2 2/2] pem: load engine keys

2016-12-06 Thread Roumen Petrov
Hi Richard, Richard Levitte wrote: [SNIP] James.Bottomley>1. We agreed that usability is greatly enhanced if openssl simply loads James.Bottomley> a key when presented with the file/uri etc. without the user having James.Bottomley> to specify what the format of a key is