Open GoogleCodeExporter opened 9 years ago
Note that there real limits to this.
The encrypted data was written to flash memory and a typical OS won't actually erase the data when overwritten -- it'll simply write the data elsewhere and, maybe, at some point in the future, overwrite the original data.
On top of this, an attacker that knows such a feature exists will simply make a copy of the encrypted data before trying to force the password from someone.
A more general solution would be to provide different lists for different passwords. Thus, if pressured, you could just reveal a "honeypot" password giving an empty list or fake data. Add a chunk of random data to the file contents and it becomes impossible to tell, upon opening one secrets list, to know if there are parallel secrets lists protected by other passwords.
This needs to be done with nested lists, where you have to enter multiple passwords to unlock each new layer. That's likely to be too difficult to be useful to all but a few truly hardcore security experts and they would have more advanced systems to start with.
Still, you don't have to be fully secure to stop a nosy airport security guard in an authoritarian country.
Original issue reported on code.google.com by
twzgerald@gmail.com
on 16 Jul 2014 at 1:05