Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

On 9/29/2015 12:13 PM, Michael König wrote: Hi everyone, I got into a situation where i want to check what protocol version and cipher was used for an SSL connection. (HTTPS) I found CURLINFO_TLS_SESSION and it looked like it might give me access to the information i need, but it does not.

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

Ray Satiro via curl-library wrote: On 10/7/2015 9:10 AM, Daniel Stenberg wrote: On Wed, 7 Oct 2015, Rich Gray wrote: For what it's worth, CURLINFO_TLS_SSL_PTR seems more meaningful to me than CURLINFO_TLS_SESSION_V2. For maximum clarity, maybe CURLINFO_TLS_CTX_PTR could be added as an alias

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

On 10/7/2015 9:10 AM, Daniel Stenberg wrote: On Wed, 7 Oct 2015, Rich Gray wrote: For what it's worth, CURLINFO_TLS_SSL_PTR seems more meaningful to me than CURLINFO_TLS_SESSION_V2. For maximum clarity, maybe CURLINFO_TLS_CTX_PTR could be added as an alias for CURLINFO_TLS_SESSION and the

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

Ray Satiro via curl-library wrote: I plan to put in the CURLINFO_TLS_SESSION_V2 implementation (credit to Michael Kaufmann for suggesting that) instead of the CURLINFO_TLS_SSL_PTR. For what it's worth, CURLINFO_TLS_SSL_PTR seems more meaningful to me than CURLINFO_TLS_SESSION_V2. For maximum

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

On Wed, 7 Oct 2015, Rich Gray wrote: For what it's worth, CURLINFO_TLS_SSL_PTR seems more meaningful to me than CURLINFO_TLS_SESSION_V2. For maximum clarity, maybe CURLINFO_TLS_CTX_PTR could be added as an alias for CURLINFO_TLS_SESSION and the later "depreciated". I'm with Rich here. We

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

On 10/6/2015 6:21 AM, Frank Meier wrote: Hi Here is another idea, piggyback on CURLINFO_TLS_SESSION instead. CURLINFO_TLS_SESSION_V2 returns OpenSSL SSL * but is otherwise the same as CURLINFO_TLS_SESSION: https://github.com/jay/curl/compare/master...jay:curlinfo_tls_session_v2?expand=1

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

Hi Here is another idea, piggyback on CURLINFO_TLS_SESSION instead. CURLINFO_TLS_SESSION_V2 returns OpenSSL SSL * but is otherwise the same as CURLINFO_TLS_SESSION: https://github.com/jay/curl/compare/master...jay:curlinfo_tls_session_v2?expand=1 +1 I'd really like seeing this patch being

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

> Ray Satiro via curl-library hat am 2. Oktober 2015 > um 20:34 geschrieben: > > > On 10/2/2015 3:39 AM, Michael König wrote: > >> Ray Satiro via curl-library hat am 1. Oktober > >> 2015 > >> um 21:03 geschrieben: > >> > >> Here is

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

On 10/2/2015 3:39 AM, Michael König wrote: Ray Satiro via curl-library hat am 1. Oktober 2015 um 21:03 geschrieben: Here is another idea, piggyback on CURLINFO_TLS_SESSION instead. CURLINFO_TLS_SESSION_V2 returns OpenSSL SSL * but is otherwise the same as

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

> Ray Satiro via curl-library hat am 1. Oktober 2015 > um 21:03 geschrieben: > > Here is another idea, piggyback on CURLINFO_TLS_SESSION instead. > CURLINFO_TLS_SESSION_V2 returns OpenSSL SSL * but is otherwise the same > as CURLINFO_TLS_SESSION: > >

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

On 9/30/2015 8:15 PM, Ray Satiro wrote: I started a draft [2] of CURLINFO_TLS_SSL_PTR to get the active SSL object for all SSL backends. In the case of DarwinSSL and WinSSL it appears the CTX is the SSL object, please correct me if this is wrong. Just written not built, I could use some

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

On 9/29/2015 12:13 PM, Michael König wrote: Hi everyone, I got into a situation where i want to check what protocol version and cipher was used for an SSL connection. (HTTPS) I found CURLINFO_TLS_SESSION and it looked like it might give me access to the information i need, but it does not.

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

Should we consider providing another pointer for the OpenSSL backend? Sure, I'm open for discussions and solutions! Yes, please consider this. I propose to add a new CURLINFO constant, because the existing API must not be changed (backwards compatibility). We could call it

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

Michael Kaufmann wrote: Should we consider providing another pointer for the OpenSSL backend? Sure, I'm open for discussions and solutions! Yes, please consider this. I propose to add a new CURLINFO constant, because the existing API must not be changed (backwards compatibility). We could

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

On Wed, 30 Sep 2015, Ray Satiro via curl-library wrote: I don't know why the SSL object isn't exposed. It's been proposed before, I don't remember what happened. (Not that I think it really matters WHY we did things the way we did in the past but the question should rather be what do we do

Re: CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

On 9/30/2015 6:32 AM, Daniel Stenberg wrote: On Wed, 30 Sep 2015, Ray Satiro via curl-library wrote: I don't know why the SSL object isn't exposed. It's been proposed before, I don't remember what happened. (Not that I think it really matters WHY we did things the way we did in the past but

CURLINFO_TLS_SESSION with OPENSSL returns SSL_CTX instead of SSL

Hi everyone, I got into a situation where i want to check what protocol version and cipher was used for an SSL connection. (HTTPS) I found CURLINFO_TLS_SESSION and it looked like it might give me access to the information i need, but it does not. When using the OpenSSL backend