You would use a 'fake' container for safe work that you don't mind revealing, while only entering your 'secret' container only when, and alway when, doing work you want to keep secret. This way. there isn't really any 'fake' data, just different data.
Truecrypt didn't generate fake date, you (the user) did. E.g. put porn on "show to thugs" partition and "Death star plans" on "true" encrypted partition.
Poop porn? Also, besides keeping that, and starting VLC muted in the background from time to time to keep plausibility, you would use the porn tainted partition for your everyday stuff. Hacker news, etc.
Comments
But isn't it a non-trivial problem to generate plausible fake data?
You would use a 'fake' container for safe work that you don't mind revealing, while only entering your 'secret' container only when, and alway when, doing work you want to keep secret. This way. there isn't really any 'fake' data, just different data.
Truecrypt didn't generate fake date, you (the user) did. E.g. put porn on "show to thugs" partition and "Death star plans" on "true" encrypted partition.
Yeah, I know. My point is that it's hard to generate a plausible alternate dataset for something like that.
"So, the decrypted hard drive says that you used the computer exactly once to put pornography on the computer and then never use it again ..."
Poop porn? Also, besides keeping that, and starting VLC muted in the background from time to time to keep plausibility, you would use the porn tainted partition for your everyday stuff. Hacker news, etc.