How to add my own crypto with openssl libs

Hi, I have written a my code for AES_CCM ciper suite. I want to use the openssl libray mainly *libssl.so* to do the handshake and part of the record layer part . Because I want to run this on the embedded target(my target has very less memory) I dont want to put the libcrypto.so provide by

RE: How to add my own crypto with openssl libs

You might be better served using a smaller library like PolarSSL for an embedded target. -Sam Kerr From: owner-openssl-...@openssl.org [mailto:owner-openssl-...@openssl.org] On Behalf Of Indtiny S Sent: Friday, February 14, 2014 6:10 AM To: openssl-users@openssl.org;

Re: How to add my own crypto with openssl libs

You can hook your engine to the crypto library to do the enc/dec. But I don't think you can completely avoid the libcrypto.so. Someone please correct me if I am wrong. On 14 February 2014 16:40, Indtiny S indt...@gmail.com wrote: Hi, I have written a my code for AES_CCM ciper suite. I want

Re: Order of Cleanup to avoid memory leaks?

Here's the code that's causing the leak. It only happens on a non-existent file. BIO bio = BIO_new_file(does-not-exist, r); // dh = PEM_read_bio_DHparams(bio, NULL, NULL, NULL); I still don't know how to clear it, however. Is there some *_cleanup() I missed? Does order matter? Jeff On Mon,

More CRL question

It is understood that if CRL check is set but CRL file is not included, openSSL will report ERR(3). What happens, if we have a 3-tier CAs and the CRL from the middle tier is not included. Will openSSL report error, with the setting of X509_V_FLAG_CRL_CHECK_ALL? - rosect190