>
> The usual defense against this attack is to mix some random information
> into the beginning of the plaintext.
>
> A better defense: use a different key each time. Encrypt the session key
> separately.
>
And /or start encrypting after the fixed header.
Best regards,
Frank.
I will be out of the office starting 2005-07-25 and will not return until
2005-08-19.
I will respond to your message when I return.
>
> >
> > Re: 3) Six million and (not) counting:
> >I don't really know, but are you perhaps on a FAT filesystem with a
> > 2GByte filesize limit?
> No. Its an ext2 :-(
> When the DB got locked the partition usage was just 6%!
>
FILE SIZE limitation is not the same as PARTITION SIZE
I am doing a port of SQLite to the Blackfin processor.
The Blackfin has a very simple kernel (called VDK) and we have a simple
file system.
We will use SQLite only to do queries on the database (it is a fixed
database, which we prepare on the PC).
I assume that I can make a very lightweight
While cross-compiling sqlite3.2.1, my Blackfin C compiler gives the
following warning:
".\src\pager.c", line 1342: cc0111: {D} warning: statement is unreachable
assert( rc==SQLITE_OK );
The context is:
/* This loop terminates either when the readJournalHdr() call returns
**
My previous post was not accurate.
In fact, my data was unsigned, but sqlite3explorer DISPLAYS numbers > 2^31
as negative numbers.
Maybe sqlite3explorer could use 64-bit integers to display numeric integer
values.
Best regards,
Frank.
To the author of sqlite3explorer: Thanks! It's a great tool!!
I would like to support the tool by submitting 2 problems I've found:
1. The rowid (implicit column) is not displayed.
2. I have a table with signed 32-bit integers. Doing queries with negative
values doesn't work. I have to specify
Never mind, the native compiler DOES support 64-bit integers :-)
I assume something is missing in your example.
There seems to be no connection between the 'result' variable and the
sw_cell() calls.
> result = sw_query(sqlite_handle, "SELECT * FROM table");
> printf("Data %s, %s, %s\n", sw_cell(0, 0), sw_cell(0, 1), sw_cell(0,
2));
best regards
Frank
I've asked this two weeks ago but no reply yet...
I've got one application that writes to the database, and one that reads
from it. When a table in the database has changed, the reading
application needs to know that. Of course I can send a signal from the
writer to the reader app, but if
Why not have config.h statically contain:
#define SQLITE_PTR_SZ (sizeof(char*))
Wouldn't that be much easier?
Best regards,
Frank.
Is it possible for a C application to get a callback as soon as a
database's content has changed?
Best regards,
Frank.
12 matches
Mail list logo