From: owner-openssl-us...@openssl.org On Behalf Of Gregory Sloop
Sent: Monday, September 15, 2014 22:50
And, one more question:
How can I tell what format/encryption my pkcs12 files are in?
[I believe for Android platform use, I need p12 certs/keys - so I'm working
on the
Hello,
I am currently focusing on matching various digests that we talked about
earlier in the thread.
1. Computing the hash of the executable (excluding the areas as defined by MS)
and matching it with the value stored in spcIndirectData. This is straight
forward and figured out.
2.
[SNIP]
However this looks like the key is encrypted with 3DES, but I exported it
from the Cert+Key with -aes256 - so I'm puzzled why I'd have a 3DES
encrypted p12.
DT You thought you did but you didn't.
DT The doc is a bit subtle, but the -$cipher option is listed under PARSING.
DT It
Hi Thulasi,
Thanks for the response.
But my point is little different here. I have a generic HTTP client,
that talks to SSL 3.0 as well as TLS 1.x enabled server.
And as mentioned earlier, I have disabled SSLv2.
Now, when I talk to any server, shouldn't the client be sending
SSLv3(SSL 3.0) in
As Thulasi wrote, SSLv23_client_method supports *ALL* protocols that your
library supports by default. The name of the function is just historical and
should be ignored. From the documentation:
If the cipher list does not contain any SSLv2 ciphersuites (the default cipher
list does not) or
On Mon, Sep 15, 2014 at 11:19:52AM +0530, Thulasi Goriparthi wrote:
I suggest you try disabling TLS 1.0 along with SSL2 if you want to force
your client to use SSL3 without changing the context's method.
SSL_CTX_set_options(ctx, SSL_OP_ALL|
