Thanks All. Conclusion: RSA_public_decrypt/encrypt is not supported in FIPS mode. For making FIPS compliance I have to replace signing algorithm with EVP_sign*() and verification by EVP_verify*()
Thanks, Gayathri On Thu, Nov 13, 2014 at 9:19 PM, Dr. Stephen Henson <st...@openssl.org> wrote: > On Thu, Nov 13, 2014, Gayathri Manoj wrote: > > > Hi Stephen, > > > > I am extracting raw digest by using then below command. > > > > /* decrypt the content using the RSA pub key */ > > elen = RSA_public_decrypt(sLen, sData, ebuf, rsaKey, RSA_PKCS1_PADDING); > > > > /* comuptes SHA1 hash*/ > > SHA1_Init(&ctx); > > SHA1_Update(&ctx, dataBlk, dataLen); > > SHA1_Final(hash, &ctx); > > > > /* compare the signed data from phone and locally generated one */ > > if (memcmp(hash, ebuf, elen) == 0) > > authenticated = true; > > > > >From the baove answer i cam eto know Its not possible to make FIPs > > compliance in openssl-0.9.8za without modifying the signature schema > which > > is sent by some other entity ( In this case sData). and in the above > > example , no other way we can check the authentication. Please update me > > if the above sentence is wrong. > > > > It's not just an OpenSSL 0.9.8za thing: using a raw digest in that was is > not > a FIPS approved signature scheme so this would apply to any library you > used. > Sure some libraries might let you do this anyway (as OpenSSL will if you > set > the appropriate override flags) but the resulting application wouldn't be > compliant. > > Steve. > -- > Dr Stephen N. Henson. OpenSSL project core developer. > Commercial tech support now available see: http://www.openssl.org > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager majord...@openssl.org >
