You present a new and novel approach to corrupting the database, which is to combine a database file with a journal from a different database into the same directory. We'll be thinking about what to prevent this attack in the 6 days that remain before we freeze the 3.0.0 database format.
It gets worse than that, or more specifically, there is another variant. Someone could make a backup of of the journal file for a database while a transaction is active (advisory locks wouldn't prevent it) and then sometime later they would put that file back. We would see a similar kind of corruption, but certain kinds of solutions that may work with journal files from other databases wouldn't fix this one.
I will supply another email shortly with a proposed solution to the problems.
-- Darren Duncan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
