Best format for enveloped & signed content

nefit to one approach? I apologize if this is a newbie question (I'm sure it is); I just didn't want to get started on this project in one format only to discover that I've made a dreadful mistake. Cheers, -- Jeremy R. NovaWave Solutions__

Best format for enveloped & signed content

nefit to one approach? I apologize if this is a newbie question (I'm sure it is); I just didn't want to get started on this project in one format only to discover that I've made a dreadful mistake. Cheers, -- Jeremy R. NovaWave Solutions__

Re: General Question

They are two different network protocols which both implement cryptography. OpenSSL is primarily used by developers behind the scenes and not directly by users (though there is an "openssl" command-line tool that exposes many of OpenSSL's capabilities). I assume the "command prompt featur

Read DER-encoded RSA public key in memory?

(in C mode), for what it's worth. -- Jeremy R. NovaWave Solutions __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automat

Re: Read DER-encoded RSA public key in memory?

code : BIO* keyBio = BIO_new_mem_buf(TESTING_PUBLIC_KEY, sizeof(TESTING_PUBLIC_KEY)); public_key = d2i_PUBKEY_bio(keyBio, NULL); That's it! I hope this will help. Cheers, -- Mounir IDRASSI IDRIX http://www.idrix.fr Jeremy R. wrote: I'm trying to make a simple application which uses a 4096

Using BIO_f_base64 on in-memory data

When it's -1, BIO_should_retry() and BIO_should_read() both return true but BIO_should_write() returns false. I don't know where to go from here. I'm an OpenSSL newbie, and I'd appreciate any help you could offer. My Google searches haven't turned up anything u

Re: Using BIO_f_base64 on in-memory data

Never mind my question. Apparently the Base64 interpreter only accepts data if it's newline-terminated. Sorry for the bother. On 21-Jul-09, at 5:59 PM, Jeremy R. wrote: Hello: I'm trying to do something that should be fairly simple: read Base64- encoded data in memory block A an

EVP_Open* with a public key

ant. I know it's not that hard to extract the key from the client executable, but I'm more concerned about eavesdropping third parties who will not have access to the client executable. -- Jeremy R. NovaWave Solutions _

Re: EVP_Open* with a public key

Thanks for your reply, first of all. I'm by no means an expert in cryptography (and obviously not on OpenSSL), and I'd appreciate any insight you can provide. On 24-Jul-09, at 7:14 PM, David Schwartz wrote: Jeremy R. wrote: I'm writing a client application that needs

Re: EVP_Open* with a public key

On 25-Jul-09, at 6:30 AM, David Schwartz wrote: Jeremy R.: Thanks for your reply, first of all. I'm by no means an expert in cryptography (and obviously not on OpenSSL), and I'd appreciate any insight you can provide. So that's a good reason not to invent your own solution

Re: EVP_Open* with a public key

ems inelegant. On 25-Jul-09, at 9:56 PM, David Schwartz wrote: Jeremy R. wrote: It's also a good reason to understand why my solution isn't valid (assuming it isn't) so that I have the understanding to correctly engineer future programs that use cryptography. Because it relie

Re: EVP_Open* with a public key

On 27-Jul-09, at 12:05 PM, David Schwartz wrote: Jeremy R. wrote: Okay, forgive my ignorance, but isn't the most common way of signing data simply taking a cryptographic hash (SHA-1, RIPEMD-160, WHIRLPOOL, etc.) and then encrypting it with a public-key technology? Yes, that'

Re: EVP_Open* with a public key

On 27-Jul-09, at 9:59 PM, Dave Thompson wrote: From: owner-openssl-us...@openssl.org On Behalf Of David Schwartz Sent: Monday, 27 July, 2009 12:06 Jeremy R. wrote: Okay, forgive my ignorance, but isn't the most common way of signing data simply taking a cryptographic hash (SHA-1, R