1
RSA_check_key(3) OpenSSL RSA_check_key(3)
NNNNAAAAMMMMEEEE
RSA_check_key - validate private RSA keys
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
#include
int RSA_check_key(RSA *rsa);
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
This function validates RSA keys. It checks that pppp and qqqq are
in fact prime, and that nnnn ==== pppp****qqqq.
It also checks that dddd****eeee ==== 1111 mmmmoooodddd ((((pppp----1111****qqqq----1111)))), and that ddddmmmmpppp1111,
ddddmmmmqqqq1111 and iiiiqqqqmmmmpppp are set correctly or are NNNNUUUULLLLLLLL.
As such, this function can not be used with any arbitrary
RSA key object, even if it is otherwise fit for regular RSA
operation. See NNNNOOOOTTTTEEEESSSS for more information.
RRRREEEETTTTUUUURRRRNNNN VVVVAAAALLLLUUUUEEEE
_R_S_A__c_h_e_c_k__k_e_y() returns 1 if rrrrssssaaaa is a valid RSA key, and 0
otherwise. -1 is returned if an error occurs while checking
the key.
If the key is invalid or an error occurred, the reason code
can be obtained using _E_R_R__g_e_t__e_r_r_o_r(3).
NNNNOOOOTTTTEEEESSSS
This function does not work on RSA public keys that have
only the modulus and public exponent elements populated. It
performs integrity checks on all the RSA key material, so
the RSA key structure must contain all the private key data
too.
Unlike most other RSA functions, this function does nnnnooootttt 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 nnnnoooo 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.
BBBBUUUUGGGGSSSS
A method of verifying the RSA key using opaque RSA API
functions might need to be considered. Right now
_R_S_A__c_h_e_c_k__k_e_y() 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
1.0.2d Last change: 2015-07-09 1
RSA_check_key(3) OpenSSL RSA_check_key(3)
"_c_h_e_c_k__k_e_y()" handler to the RSA_METHOD function table so
that alternative implementations can also provide their own
verifiers.
SSSSEEEEEEEE AAAALLLLSSSSOOOO
_r_s_a(3), _E_R_R__g_e_t__e_r_r_o_r(3)
HHHHIIIISSSSTTTTOOOORRRRYYYY
_R_S_A__c_h_e_c_k__k_e_y() appeared in OpenSSL 0.9.4.
1.0.2d Last change: 2015-07-09 2