> From: owner-openssl-us...@openssl.org On Behalf Of Marc Phillips
> Sent: Thursday, 05 August, 2010 11:20
> Ger Hobbelt wrote:
> > Got some sample data to show which makes the bugger fail?
>
> sqlite3 /tmp/MyTestsqlite.db
> SQLite version 3.3.6
> Enter ".help" for instructions
> sqlite> CREATE
> If you want to encrypt a database, have you considered SQLCipher
> (http://www.zetetic.net/code/sqlcipher)? It is free and uses OpenSSL.
I'm not encrypting it (the data is encrypted via the app already anyway),
I'm simply b64 encoding it; thanks though, this might be useful for other
things.
Hi Marc,
If you want to encrypt a database, have you considered SQLCipher
(http://www.zetetic.net/code/sqlcipher)? It is free and uses OpenSSL.
Jeff
On Thu, Aug 5, 2010 at 11:19 AM, Marc Phillips wrote:
> Ger Hobbelt wrote:
>> Got some sample data to show which makes the bugger fail?
>
> sqlit
Ger Hobbelt wrote:
> Got some sample data to show which makes the bugger fail?
sqlite3 /tmp/MyTestsqlite.db
SQLite version 3.3.6
Enter ".help" for instructions
sqlite> CREATE TABLE test (id INTEGER primary key AUTOINCREMENT, test TEXT);
sqlite> .quit
encode:
bmem = BIO_new(BIO_s_mem());
b64 = BI
Got some sample data to show which makes the bugger fail?
On Thu, Aug 5, 2010 at 4:58 AM, Marc Phillips wrote:
> I mean if try to decode, it stops 15 bytes in. If I read
> the original file, and print out byte 15, it's a \n.
>
> I tried using BIO_FLAGS_BASE64_NO_NL, which then failes on encode.
> I'm not sure quite what you mean here. bio_b64 by default
> adds \n linebreaks every 64 chars when encoding (output)
I mean if try to decode, it stops 15 bytes in. If I read
the original file, and print out byte 15, it's a \n.
I tried using BIO_FLAGS_BASE64_NO_NL, which then failes on encode
> From: owner-openssl-us...@openssl.org On Behalf Of Marc Phillips
> Sent: Tuesday, 03 August, 2010 23:48
> I'm having an issue with using base64 decode. I can encode fine,
> and can decode strings just fine, but am having an issue
> decoding (specifically) a sqlite database.
>
> Here's my enco
