summaryrefslogtreecommitdiff
path: root/src/lib/libssl/ssl_transcript.c
diff options
context:
space:
mode:
authortb <>2022-05-10 19:42:52 +0000
committertb <>2022-05-10 19:42:52 +0000
commit60292e3c622f4c29a5af160d34b90580ef8c6d03 (patch)
tree60fe30f710c955610cc67d15f8ffd93470272bb4 /src/lib/libssl/ssl_transcript.c
parent87bc747a621099ecbcaca15ffcd7fce26af82d67 (diff)
downloadopenbsd-60292e3c622f4c29a5af160d34b90580ef8c6d03.tar.gz
openbsd-60292e3c622f4c29a5af160d34b90580ef8c6d03.tar.bz2
openbsd-60292e3c622f4c29a5af160d34b90580ef8c6d03.zip
X509_check_ca() has 5 return values but still can't fail
The values 0, 1, 3, 4, 5 all have some meaning, none of which is failure. If caching of X509v3 extensions fails, returning X509_V_ERR_UNSPECIFIED, i.e., 1 is a bad idea since that means the cert is a CA with appropriate basic constraints. Revert to OpenSSL behavior which is to ignore failure to cache extensions at the risk of reporting lies. Since no return value can indicate failure, we can't fix this in X509_check_ca() itself. Application code will have to call (and check) the magic X509_check_purpose(x, -1, -1) to ensure extensions are cached, then X509_check_ca() can't lie. ok jsing
Diffstat (limited to 'src/lib/libssl/ssl_transcript.c')
0 files changed, 0 insertions, 0 deletions