This is the trace from the crash dump. I've added some additional info, in *Bold*. But, again, the crash is likely something in my code which I need to fix. I'm wondering why FIPS mode wants to do an encryption operation when I asked for a signing operation. Could it be that FIPS mode encrypts some random data to get a better random number before entertaining the signature?
Thoughts? 04-25 12:11:51.189: I/DEBUG(127): backtrace: 04-25 12:11:51.189: I/DEBUG(127): #00 pc 000134b2 /data/app-lib/com.mycompany.app.pkcs7.c-1/libbaimobilemw.so (GetAttributeValue(unsigned long, CK_ATTRIBUTE*, unsigned long)+265) 04-25 12:11:51.189: I/DEBUG(127): #01 pc 000137fb /data/app-lib/com.mycompany.app.pkcs7.c-1/libbaimobilemw.so (GetKeyComponentsFromPubKeyObject(unsigned long, unsigned char**, unsigned int*, unsigned char**, unsigned int*)+42) 04-25 12:11:51.189: I/DEBUG(127): #02 pc 00014f37 /data/app-lib/com.mycompany.app.pkcs7.c-1/libbaimobilemw.so (BAL_C_EncryptInit+50) 04-25 12:11:51.189: I/DEBUG(127): #03 pc 000014a9 /data/app-lib/com.mycompany.app.pkcs7.c-1/libbaiengine.so *(pkcs11_rsa_encrypt)* 04-25 12:11:51.189: I/DEBUG(127): #04 pc 00081a44 /data/data/com.mycompany.app.pkcs7.c/files/libcrypto.so.1.0.0 (FIPS_rsa_sign_digest+220) *04-25 12:11:51.189: I/DEBUG(127): #05 PKCS7_sign* -- View this message in context: http://openssl.6102.n7.nabble.com/Bug-in-call-to-an-Engine-during-PKCS7-sign-or-not-tp44872p44917.html Sent from the OpenSSL - Dev mailing list archive at Nabble.com. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
