On 2013-06-28 1:43, Dave Thompson wrote:
From: owner-openssl-us...@openssl.org On Behalf Of Lukas Haase
Sent: Thursday, 27 June, 2013 04:46
snip previous
I think I found the problem but I am unsure how to deal with it :-(
There are two ways to create a signature: The original message can
# This is Microsoft's use of the othername type to embed the UPN which is
an arbitrary field with no meaning in the x509 standard and therefore not
parsed by the openssl command x509. You can dump it by discovering the byte
offset of the SAN with an ASN1 browser like this:
--
View this
From: owner-openssl-us...@openssl.org On Behalf Of Tanmoy Sinha
Sent: Friday, 28 June, 2013 04:29
I am using a client application program which uses OpenSSL version
1.0.0h. I configured TLSv1.2 and I have set the cipher suite only as
TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 [...but] Client Hello
