I am getting the same problem (various SSL errors after a successful
negotiation) with an SMTP server I've written in Ruby, and I'm stuck
with it
I've resorted to tracing through the Postfix SSL/TLS code to see how
they handle it, and it looks like they just keep retrying the
operation until its s
On 05/18/2012 06:03 AM, kthiru...@inautix.co.in wrote:
Team,
Had a query in the certs that we load,
The CA's provide our certs in .p12 format, which we need to convert to a .pem and load to SSL
structure during initialization.
On converting to .pem, it is in the following format, "Private Key
Team,
Had a query in the certs that we load,
The CA's provide our certs in .p12 format, which we need to convert to a
.pem and load to SSL structure during initialization.
On converting to .pem, it is in the following format, "Private Key, CA
Certs and Domain Certificate".
In our code, we use
Hello all, hope someone can help.
I upgraded from 1.0.0d to 1.0.1c and immediately started getting this error:
error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
It occurs during SMTP after successful negotiation. Oddly, the first command
after negotiation works, but not the seco
Hi,
I am trying to add extra extensions to certain certificates that I
sign with my own CA.
1) I'd like all server generated certificates to have:
basicConstraints = CA:false
and one of the certificates to have:
extendedKeyUsage = serverAuth
I created an extra section called new_section in m
Hi,
What would be the unique names with which I can store CA certificates in
file system?
I understand that issuer-id and serial number are the unique identifiers
for a certificate. But using this name for a certificate file name makes it
very long and also introduces some characters like "@,=" et
