On 12/21/2011 8:31 PM, harrije wrote:
Which OpenSSL version was it?
It was for version 1.0.0e.
It would be nice if the Configure script for VC-WIN32 added this option
automatically. Alternatively the INSTALL.W32 instructions could have a
warning that on x64 PCs to use:
perl Configure VC-W
iew this message in context:
http://old.nabble.com/Malformed-Certificate-Created-for-Windows-but-Not-Linux-tp32983415p33019307.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
__
OpenSSL Proj
On 12/17/2011 1:36 AM, harrije wrote:
The certificate malformation was for the Validity fields of notBefore and
notAfter. Turns out the problem was how I built it. I followed the
instructions in INSTALL.W32 because I needed to link the results with other
W32 binaries, however I was building on an
>
>
--
View this message in context:
http://old.nabble.com/Malformed-Certificate-Created-for-Windows-but-Not-Linux-tp32983415p32989637.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
__
OpenSSL
On Thu, Dec 15, 2011, harrije wrote:
>
> I have not had any success in my search for a known issue with malformed
> client certificates generated by openssl 1.0.0e for Windows. Before I invest
> too much time trying to debug the issue, I wanted to query whether others
> may have a clue on cause a
Just to clarify, my references to version 9.8e should read 0.9.8e
--
View this message in context:
http://old.nabble.com/Malformed-Certificate-Created-for-Windows-but-Not-Linux-tp32983415p32983417.html
Sent from the OpenSSL - User mailing list archive at Nabble.com
routines:PEM_ASN1_read_bio:ASN1 lib:pem_oth.c:83:
Does anyone have an idea of what went wrong with the Windows version?
--
View this message in context:
http://old.nabble.com/Malformed-Certificate-Created-for-Windows-but-Not-Linux-tp32983415p32983415.html
Sent from the OpenSSL - User mailing list archive at
