] Bug: SQLite Encryption Extension And Backup API
On Wed, Apr 6, 2011 at 8:21 AM, Ulric Auger <ul...@gtechna.com> wrote:
Hi,
I think I found a bug creating an encrypted backup.
The source database is encrypted using key:
aes256:A94A8FE5CCB19BA61C4C0873D391E987982FBBD3
The
On Wed, Apr 6, 2011 at 8:21 AM, Ulric Auger wrote:
> Hi,
>
> I think I found a bug creating an encrypted backup.
>
>
>
> The source database is encrypted using key:
>
> aes256:A94A8FE5CCB19BA61C4C0873D391E987982FBBD3
>
>
>
> The source database is readable, I can run select
April 7, 2011 10:13
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Bug: SQLite Encryption Extension And Backup API
Hi,
sorry.. my fault. It should be:
if (zKey != NULL)
{
sqlite3_key(pBackupDb, NULL, 0);
sqlite3_rekey(pBackupDb, zKey, strlen(zKey));
}
Thats works for me..
Marcu
Hi,
sorry.. my fault. It should be:
if (zKey != NULL)
{
sqlite3_key(pBackupDb, NULL, 0);
sqlite3_rekey(pBackupDb, zKey, strlen(zKey));
}
Thats works for me..
Marcus
On 07.04.2011 15:58, Ulric Auger wrote:
> It didn't change anything to call sqlite3_key twice as you suggested.
>
>
It didn't change anything to call sqlite3_key twice as you suggested.
I'm using SQLite 3.7.4 with SEE (SEE v3.7.5 is not available from the SEE
download page, that is strange)
I hope SQLite team can look into this.
Ulric
___
sqlite-users mailing list
On 06.04.2011 14:21, Ulric Auger wrote:
> Hi,
>
> I think I found a bug creating an encrypted backup.
..
>
>
>
> When I use the following function to create a backup of the database, the
> backup database becomes unreadable.
...
>
>
>
>rc = sqlite3_open(zFilename,);
>
>if( rc==SQLITE_OK
Hi,
I think I found a bug creating an encrypted backup.
The source database is encrypted using key:
aes256:A94A8FE5CCB19BA61C4C0873D391E987982FBBD3
The source database is readable, I can run select queries and insert data
with no problem.
When I use the following function to create a
7 matches
Mail list logo