The error that comes is that
OpenSSL uplink (0x08d) OpenSSL_addlink
I am using the privkey.pem file with the passphrase
-Original Message-
From: owner-openssl-...@openssl.org
[mailto:owner-openssl-...@openssl.org] On Behalf Of Dave Thompson
Sent: Wednesday, June 13, 2012 8:04 AM
Kamlesh Mishra would like to recall the message, PEM_read_PrivateKey throws
error in windows.
The error that I get is below
OPENSSL_Uplink(100EC020,08): no OPENSSL_Applink
I am using the privkey.pem with the passphrase.
Thanks
Kamlesh Mishra
-Original Message-
From: owner-openssl-...@openssl.org
[mailto:owner-openssl-...@openssl.org] On Behalf Of Dave Thompson
Sent: Wednesday,
This is regarding openssl renegotiation issue in client server
communication.The openssl version is 1.0.1c.
The client and server are establishing the SSL connection using blocking
sockets and communication is fine.The client sends the data and server
receives and send back to client.
When
Hi.
Attached is a patch that changes the behavior of X509_verify_cert in
crypto/x509/x509_vfy.c
While copying the cert chain into the X509_STORE_CTX, before adding a
cert, a check is done to see if we could reach one of our trust anchors
instead.
This solves the problem with a certificate chain
From: owner-openssl-...@openssl.org On Behalf Of Kamlesh Mishra
Sent: Wednesday, 13 June, 2012 09:27
The error that I get is below
OPENSSL_Uplink(100EC020,08): no OPENSSL_Applink
I am using the privkey.pem with the passphrase.
This is an issue with (most?) Windows file I/O
by OpenSSL,
