diff options
author | Richard Levitte <levitte@openssl.org> | 2002-07-18 23:11:24 +0400 |
---|---|---|
committer | Richard Levitte <levitte@openssl.org> | 2002-07-18 23:11:24 +0400 |
commit | 290416db2aab621d5a27989a61672b547a213149 (patch) | |
tree | 52da43e912e0b2cd04cd1b2fc02823542459ff93 /doc | |
parent | ff192dce10d420cdb12055becc4e11dffde25407 (diff) |
Explain why RSA_check_key() doesn't work with hard keys.
PR: 86
Diffstat (limited to 'doc')
-rw-r--r-- | doc/crypto/RSA_check_key.pod | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/doc/crypto/RSA_check_key.pod b/doc/crypto/RSA_check_key.pod index 79fed753ad..5737ecdc3e 100644 --- a/doc/crypto/RSA_check_key.pod +++ b/doc/crypto/RSA_check_key.pod @@ -28,12 +28,21 @@ RSA_check_key() returns 1 if B<rsa> is a valid RSA key, and 0 otherwise. If the key is invalid or an error occurred, the reason code can be obtained using L<ERR_get_error(3)|ERR_get_error(3)>. +=head1 NOTES + +RSA_check_key() can only check soft keys. If given hard keys, i.e. keys +that were retreived from an ENGINE (with ENGINE_load_private_key()), +RSA_check_key() will always return 0, as if the key was invalid. The +reason is that the private components B<p>, B<q> and B<d> are normally +not available to OpenSSL for hard keys, and the checks can therefore not +be done. + =head1 SEE ALSO L<rsa(3)|rsa(3)>, L<err(3)|err(3)> =head1 HISTORY -RSA_check() appeared in OpenSSL 0.9.4. +RSA_check_key() appeared in OpenSSL 0.9.4. =cut |