Re: Getting CURLE_OK with wrong pinned public key after using the correct.

2019-09-13 Thread Daniel Stenberg via curl-library
On Fri, 13 Sep 2019, Sebastian Haglund wrote: This patch fixed it for me Lovely, thanks a lot. I've ammended my PR with your update just now and will merge as soon as the CI agrees. -- / daniel.haxx.se | Get the best commercial curl support there is - from me | Private h

Re: Getting CURLE_OK with wrong pinned public key after using the correct.

2019-09-13 Thread Sebastian Haglund via curl-library
On Fri, 13 Sep 2019 at 16:41, Daniel Stenberg wrote: > On Fri, 13 Sep 2019, Daniel Stenberg via curl-library wrote: > > > I'll write up a PR for this and get back. > > Done. Can you try this and see if it fixes the behavior for you? > > https://github.com/curl/curl/pull/4347 > > That was quick,

Re: Getting CURLE_OK with wrong pinned public key after using the correct.

2019-09-13 Thread Daniel Stenberg via curl-library
On Fri, 13 Sep 2019, Daniel Stenberg via curl-library wrote: I'll write up a PR for this and get back. Done. Can you try this and see if it fixes the behavior for you? https://github.com/curl/curl/pull/4347 -- / daniel.haxx.se | Get the best commercial curl support there is - from me

Re: Getting CURLE_OK with wrong pinned public key after using the correct.

2019-09-13 Thread Daniel Stenberg via curl-library
On Fri, 13 Sep 2019, Sebastian Haglund via curl-library wrote: While adding public key pinning to a cURL c++ wrapper, I discovered that setting the wrong public key after using the correct still yields OK result (expected CURLE_SSL_PINNEDPUBKEYNOTMATCH). It seems to be related to re-using the