Thanks, this is exactly what I was looking for.
And thanks also to Peter for pointing out the already
built options openssl x509 -C
which produce the perfect C stub code.
Alberto
On Mon, 2006-02-06 at 10:04 +, Katie Lucas wrote:
> On Fri, Feb 03, 2006 at 02:54:38PM -0600, Alberto Alonso wrot
like openssl x509 -C
So you can, at compile time, build a small app which will read a
key/certificate/etc and use an i2d_* routine to DER encode it, dropping
that into a file. The file you run through a quick filter to turn into
a suitable include file making the binary data a character
array
On Fri, Feb 03, 2006 at 02:54:38PM -0600, Alberto Alonso wrote:
> I would like to be able to hard code the key/cert in the
> application instead of having files.
>
> Is there something similar to: SSL_CTX_use_PrivateKey_file
> and SSL_CTX_use_PrivateKey_file but that I can use pointers
> memory?
I would like to be able to hard code the key/cert in the
application instead of having files.
Is there something similar to: SSL_CTX_use_PrivateKey_file
and SSL_CTX_use_PrivateKey_file but that I can use pointers
memory?
If so, how do I convert the current files into that binary
data format?
I
