Hi, cruxpot,
Yes, EDKII-CryptoPkg didn't expose the underlying openssl error code, since
openssl has its internal error report / handling mechanism (e.g. use return
code for true/false, and use ERR_get_error() to retrieve error value). Current
EDKII wrapper implementation only use TRUE/FALSE to tell the result.
"Cryptest" application in CryptoPkg can be one reference about the API and
parameter. And NT32 emulator is also one convenient debug environment for your
app bug tracing. :)
Best Regards & Thanks,
LONG, Qin
From: cruxpot [mailto:[email protected]]
Sent: Thursday, October 31, 2013 4:03 AM
To: [email protected]
Subject: [edk2] OpenSSL error code question
Hi all,
I am using the edk2 CryptoPkg with OpenSSL patched and compiled according to
the EDK2 instructions.
I am running into an issue where I am trying to write an application where I
sign an Rsa key generated from RsaGetPrivateKeyFromPem call. The call
RsaPkcs1Sign is returning false and I see now way to verify which parameter is
or condition is wrong. Is there a way to do more detailed OpenSSL error
checking from within the EDK2 with CryptoPkg?
Thanks.
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
