Those are good thoughts, thanks for sharing. I like your (eg)
CURL_SSLVERSION_TLSv1 idea for example, and will look closer at it.

Thanks!

-bch

On 2/25/15, Steve Holme <steve_holme_at_hotmail.com> wrote:
> On Wed, 25 Feb 2015, bch wrote:
>
>> I'm trying to add CURLINFO_NEGOTIATED_SSL (string) and
>> my test builds are failing on doc generation
>
> I appreciate you've not submitted your patch yet but I just wanted to note
> down some of my own thoughts whilst it is fresh in my head so my apologies
> if I am jumping the gun a little:
>
> * Should (or even could) this information be added to the
> CURLINFO_TLS_SESSIONINFO without breaking ABI?
> * If not then CURLINFO_SSL_NEGOTIATED_VERSION or
> CURLINFO_TLS_NEGOTIATED_VERSION would be more in keeping with other TLS/SSL
> info.
> * Should this be a string or a long? If it was a long it could return a
> value that is compatible with CURLOPT_SSLVERSION (ie CURL_SSLVERSION_TLSv1,
> CURL_SSLVERSION_SSLv2, etc...)
>
> Kind Regards
>
> Steve
>
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http://curl.haxx.se/mail/etiquette.html
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2015-02-26