> From: Dave Thompson
> Sent: Thursday, March 03, 2011 10:35 PM
> To: openssl-users@openssl.org
>
> Also, the byte that terminates a C (narrow) string is a null
> character or null byte, sometimes called NUL (note 3 letters).
> But this character is not IN the string, it is AFTER the string.
> From: owner-openssl-us...@openssl.org On Behalf Of Vinay Kumar L
> Sent: Tuesday, 01 March, 2011 23:42
> Thanks for your reply, but OpenSSL Base64 decoding api returns NULL
> on passing Base64 encoded data. The code snippet is as follows:
I very much doubt it returns NULL. NU
Hi Jan,
Thanks for your reply, but OpenSSL Base64 decoding api returns NULL on
passing Base64 encoded data. The code snippet is as follows:
int main(int argc, char **argv)
{
char *output = unbase64("dGVzdGVuY29kaW5nCg==",
strlen("dGVzdGVuY29kaW5nCg=="));
printf("Unbase64: %s\n"
On Tue, Mar 1, 2011 at 7:00 AM, Vinay Kumar L
wrote:
> Encoding of string "testencoding" using base64 command:
>
> #base64 data.txt > encode.txt
> data.txt -> It contains only the string "testencoding"
> encode.txt -> It contains encoded data
> #cat encode.txt
> dGVzdGVuY29kaW5nCg=
Hi All,
I am doing Base64 encoding and decoding of a string "testencoding" using
OpenSSL api *BIO_f_base64, *but when Base64 encoding is done for the
same string using OpenSSL command *base64,* the last byte of encoded
data will be different than the one generated using *BIO_f_base64 *api.
Al
