summaryrefslogtreecommitdiff
path: root/src/regress/lib/libssl/tlsfuzzer
diff options
context:
space:
mode:
authortb <>2021-04-07 21:48:23 +0000
committertb <>2021-04-07 21:48:23 +0000
commit1ff6ebe4aa0a51558d12a52b713d6dfdc4486249 (patch)
treec54ab4f1f2b97ea5c7726b3ea1fdd28bf1be6ac5 /src/regress/lib/libssl/tlsfuzzer
parent6527abaa41446de00a9a123155b06733561db20d (diff)
downloadopenbsd-1ff6ebe4aa0a51558d12a52b713d6dfdc4486249.tar.gz
openbsd-1ff6ebe4aa0a51558d12a52b713d6dfdc4486249.tar.bz2
openbsd-1ff6ebe4aa0a51558d12a52b713d6dfdc4486249.zip
Avoid clobbering the error code when sending an alert
In order to fail gracefully on encountering a self-signed cert, curl looks at the top-most error on the stack and needs specific SSL_R_ error codes. This mechanism was broken when the tls13_alert_sent_cb() was added after people complained about unhelpful unknown errors. Fix this by only setting the error code from a fatal alert if no error has been set previously. Issue reported by Christopher Reid ok jsing
Diffstat (limited to 'src/regress/lib/libssl/tlsfuzzer')
0 files changed, 0 insertions, 0 deletions