3 ms·
My understanding of the feature is that is is impossible to verify whether or not you are using a hidden volume within a TC encrypted volume. Although file-hos
by FlemishBeeCycle 16y ago
My understanding of the feature is that is is impossible to verify whether or not you are using a hidden volume within a TC encrypted volume.
Although file-hosted TrueCrypt volumes (containers) do not contain any kind of "signature" either (until decrypted, they appear to consist solely of random data), they cannot provide this kind of plausible deniability, because there is practically no plausible explanation for the existence of a file containing solely random data. However, plausible deniability can still be achieved with a file-hosted TrueCrypt volume (container) by creating a hidden volume within it.
http://www.truecrypt.org/docs/?s=plausible-deniability http://www.truecrypt.org/docs/?s=plausible-deniability
- CGamesPlay 16y agoClarification: it's impossible to determine if a hidden volume exists in a TrueCrypt volume. It is trivial to determine whether a given password unlocks the main, hidden, or neither volume.
- hyperbovine 16y agoHow is it trivial to verify whether a password unlocks something the existence of which is impossible to verify?
- NinetyNine 16y agoData about the hidden volume is encrypted and kept in the second 512 bytes of the volume, where as data about the normal volume is in the first 512 bytes. If there is no hidden volume, the second 512 bytes are purely random data. It's impossible to tell an encrypted volume header apart from random data. It's very much "try, and if you fail, you either have the wrong key or the volume doesn't exist".