ippet of code laying around somewhere that does that
> given a X509 cert as input would there? It looks a bit arcane....
>
> On 1/10/2016 21:04, Judson Wilson wrote:
>
> It's always good to start with the s_client and s_server programs for
> incrementally verifying compatibil
d the problem... for an unexplained reason either the certificate or
> key were corrupt; I have added checking to make sure they're coherent, as
> apparently OpenSSL is perfectly happy to load a bogus cert (or key) without
> throwing an error, but won't present them.
>
>
>
On the client side, double check that you are creating the SSL object from
the context AFTER you set the client cert for the context, and not the
other way around.
On Sun, Jan 10, 2016 at 2:18 PM, Karl Denninger wrote:
> I'm sure this is a function of my lack of understanding of the
> documentat
I have seen several sources suggest that the following psuedo code
procedure should force a renegotiation before proceeding:
SSL_renegotiate(...);
while(SSL_renegotation_pending(...))
SSL_do_handshake(...);
I am using non-blocking I/O, and have ommitted error handling and any
lower-level I/O
