RE: Saving (and restoring) cipher context

-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Schwartz Sent: Thursday, May 31, 2007 7:17 PM To: openssl-users@openssl.org Subject: RE: Saving (and restoring) cipher context > I think your argument is based on a false premise. In the majority of

RE: Saving (and restoring) cipher context

-- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Resch Sent: Thursday, May 31, 2007 9:33 AM To: openssl-users@openssl.org Subject: RE: Saving (and restoring) cipher context If you have concerns about doing encryption client side and worry about how to securely pass the key around

RE: Saving (and restoring) cipher context

If you have concerns about doing encryption client side and worry about how to securely pass the key around you can try the oft-used strategy of using an asymmetric (RSA) public key to encrypt a randomly generated symmetric (AES) key. This encrypted symmetric key can then be safely stored with the

Re: RE; 192-bit signatures

Bob Mearns wrote: >> I'm looking to generate a short digital signature, perhaps 192 >> bits or so, using an asymmetrical algorithm. DSA seems to >> have 320 bit signatures regardless of the key size used. Is >> this really the case, or am I missing something? Ignoring for >> the moment the wi

Memory leak in OpenSSL application

any other functions I should be calling to prevent memory leaks? I would be grateful to hear from anyone who is experienced in this area. Thank you in advance. Best Regards, Jason Resch __ OpenS