X-Git-Url: https://git.openssl.org/?p=openssl.git;a=blobdiff_plain;f=doc%2Fcrypto%2FRSA_check_key.pod;h=522a6c2b5e390015809434a8c477ec08ee1e74b3;hp=c250a776e46055f0aaff27031471cd3e883845cb;hb=2afb29b480d87c4c24f830e69dfe82762e3db608;hpb=6a3fff5ecfdd78cd45ae22af3fb4bd32f98cd106 diff --git a/doc/crypto/RSA_check_key.pod b/doc/crypto/RSA_check_key.pod index c250a776e4..522a6c2b5e 100644 --- a/doc/crypto/RSA_check_key.pod +++ b/doc/crypto/RSA_check_key.pod @@ -2,38 +2,76 @@ =head1 NAME -RSA_check_key - Validate RSA keys +RSA_check_key - validate private RSA keys =head1 SYNOPSIS #include + int RSA_check_key_ex(RSA *rsa, BN_GENCB *cb); + int RSA_check_key(RSA *rsa); =head1 DESCRIPTION -This function validates RSA keys. It checks that B

and B are +RSA_check_key_ex() function validates RSA keys. +It checks that B

and B are in fact prime, and that B. +It does not work on RSA public keys that have only the modulus +and public exponent elements populated. It also checks that B, and that B, B and B are set correctly or are B. +It performs integrity checks on all +the RSA key material, so the RSA key structure must contain all the private +key data too. +Therefore, it cannot be used with any arbitrary RSA key object, +even if it is otherwise fit for regular RSA operation. + +The B parameter is a callback that will be invoked in the same +manner as L. -The key's public components may not be B. +RSA_check_key() is equivalent to RSA_check_key_ex() with a NULL B. =head1 RETURN VALUE -RSA_check_key() returns 1 if B is a valid RSA key, and 0 otherwise. --1 is returned if an error occurs while checking the key. +RSA_check_key_ex() and RSA_check_key() +return 1 if B is a valid RSA key, and 0 otherwise. +They return -1 if an error occurs while checking the key. If the key is invalid or an error occurred, the reason code can be -obtained using ERR_get_error(3). +obtained using L. + +=head1 NOTES + +Unlike most other RSA functions, this function does B work +transparently with any underlying ENGINE implementation because it uses the +key data in the RSA structure directly. An ENGINE implementation can +override the way key data is stored and handled, and can even provide +support for HSM keys - in which case the RSA structure may contain B +key data at all! If the ENGINE in question is only being used for +acceleration or analysis purposes, then in all likelihood the RSA key data +is complete and untouched, but this can't be assumed in the general case. + +=head1 BUGS + +A method of verifying the RSA key using opaque RSA API functions might need +to be considered. Right now RSA_check_key() simply uses the RSA structure +elements directly, bypassing the RSA_METHOD table altogether (and +completely violating encapsulation and object-orientation in the process). +The best fix will probably be to introduce a "check_key()" handler to the +RSA_METHOD function table so that alternative implementations can also +provide their own verifiers. =head1 SEE ALSO -rsa(3), err(3) +L, +L, +L =head1 HISTORY -RSA_check() appeared in OpenSSL 0.9.4. +RSA_check_key() appeared in OpenSSL 0.9.4. +RSA_check_key_ex() appeared after OpenSSL 1.0.2. =cut