Ok that makes sense. kinda goes with what I had been thinking, So i just add
the null character at the end of the bio before I use BIO_get_mem_data(out,
&enc_msg);
now just how to do that .
ssl bio write
mike Luich
On Fri, Aug 29, 2008 at 1:35 PM, David Schwartz <[EMAIL PROTECTED]>wrote:
>
>
> Hmm then perhaps I'm expecting the wong thing to be coming
> out. I'm using PKCS7_encrypt followed by SMIME_write_PKCS7.
> So the data is base64 encoded and in S/MIME Format.
> I just want to get this in a format that I can return as a
> string that's null terminated. So the app can use it as
Hmm then perhaps I'm expecting the wong thing to be coming out. I'm using
PKCS7_encrypt followed by SMIME_write_PKCS7. So the data is base64 encoded
and in S/MIME Format.
I just want to get this in a format that I can return as a string that's
null terminated. So the app can use it as a string.
M
> Hello everyone, here's what's driving me nuts.
> I'm sure i'm missing something simple, but why isn't the
> encrypted message coming out of
> " BIO_get_mem_data(out, &enc_msg); " Null terminated ?
> Mike Luich
Why should it be? It's not a string, it's a block of arbitrary data.
Besides, what
On Fri August 29 2008 11:35, Michael Luich wrote:
> Hello everyone, here's what's driving me nuts. I'm sure i'm missing
> something simple, but why isn't the encrypted message coming out of "
> BIO_get_mem_data(out, &enc_msg); " Null terminated ?
>
Because null is a valid encrypted value of a by
