I have the impression you want to protect (providing message integrity,
message authentication, and confidentiality) messages between a client and
a server. The options are:
1. Protect individual message with known techniques such as S/MIME, CMS
and send it in unprotected connection.
2. Protect th
On Wed, May 02, 2012, Tammany, Curtis wrote:
> > If the client certs require chain certs additional to (below
> > or beside) those in your file, and some clients are sending
> > those chain certs but other clients (e.g. Windows 7) are not,
> > that would cause the symptom without any cert(s) being
I want to send encrypted information from a client to the server via non-SSL
connections without using hardcode encryption key, i.e. a typical scenario.
Both client and server have their private key and certificate. (RAS key, PEM
format)
I am thinking of two options to exchange the encryption ke
> If the client certs require chain certs additional to (below
> or beside) those in your file, and some clients are sending
> those chain certs but other clients (e.g. Windows 7) are not,
> that would cause the symptom without any cert(s) being actually
> invalid. To test this, get the chain cert(
On Wed, May 02, 2012, Phil Pennock wrote:
> Folks,
>
> With OpenSSL 1.0.1b installed (FreeBSD), I made a couple of changes to
> Exim HEAD; one was to set SSL_MODE_AUTO_RETRY on the SSL_CTX used for
> accepting connections, so that renegotiation might theoretically work
> now. (I mention this so
Folks,
With OpenSSL 1.0.1b installed (FreeBSD), I made a couple of changes to
Exim HEAD; one was to set SSL_MODE_AUTO_RETRY on the SSL_CTX used for
accepting connections, so that renegotiation might theoretically work
now. (I mention this so as to clarify that renegotiation will likely
not work w
