Unlike Curl_ossl_connect(), the Curl_gtls_connect()
function does not send the user certificate to the
peer. In fact, it ignores the conn->data->set.cert
field completely, it always uses the anonymous credentials.
Thanks for reporting. This issue seems to not have a very
high prio with people and I personally can't test any
changes nor does this scratch any major itch on my back.
I've added this issue as KNOWN_BUGS number #27, and I'm
closing this report now until somone wants to fix it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
All right, here is a start. It's not perfect, it only works
with unencrypted private keys, but it's better than nothing,
I think. Any comments are welcome.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1110
Ouch, That is correct. Let's see if there's someone
interested in fixing this...
Logged In: YES
user_id=1110
Thanks for reporting. This issue seems to not have a very
high prio with people and I personally can't test any
changes nor does this scratch any major itch on my back.
I've added this issue as KNOWN_BUGS number #27, and I'm
closing this report now until somone wants to fix it.
Logged In: YES
user_id=644787
All right, here is a start. It's not perfect, it only works
with unencrypted private keys, but it's better than nothing,
I think. Any comments are welcome.
Logged In: YES
user_id=1110
Thanks!
I applied and committed just now.