summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/rsa/rsa_lib.c
diff options
context:
space:
mode:
authortb <>2025-01-05 15:39:12 +0000
committertb <>2025-01-05 15:39:12 +0000
commitaeaaf636a6726b17d0d27ea128a573bc90c4d04f (patch)
treecd64f6e5f9ce5fc370008ff0fd77e5e13c35c0cc /src/lib/libcrypto/rsa/rsa_lib.c
parent50987dd3b5034f6426dcbad59ec85073fc6f9c6f (diff)
downloadopenbsd-aeaaf636a6726b17d0d27ea128a573bc90c4d04f.tar.gz
openbsd-aeaaf636a6726b17d0d27ea128a573bc90c4d04f.tar.bz2
openbsd-aeaaf636a6726b17d0d27ea128a573bc90c4d04f.zip
Stop requiring the RSA_FLAG_SIGN_VER
You can set custom sign and verify handlers on an RSA method (wihch is used to create RSA private and public key handles). However, even if you set them explicitly with RSA_meth_set_{sign,verify}(3), these handlers aren't used for the sake of "backward compatibility" (with what?). In order to use them, you need to opt your objects into using the custom methods you set by setting the RSA_FLAG_SIGN_VER flag. OpenSSL 1.1 dropped this requirement and therefore nobody sets this flag anyore. Like most of the mechanically added accessors, almost nothing uses them, but, as found by kn, the yubco-piv-tool does. This resulted in a public key being passed to rsa_private_encrypt(), which of course doesn't end well. So follow OpenSSL 1.1 and drop this muppetry. This makes kn's problem with yubico-piv-tool go away. ok jsing kn
Diffstat (limited to 'src/lib/libcrypto/rsa/rsa_lib.c')
0 files changed, 0 insertions, 0 deletions