On Sat, Jan 13, 2018 at 03:44:03AM +0000, nullius via bitcoin-dev wrote: > (I think that next, I may start writing my disks with headers for LUKS, > which I do not use...) > > Whereupon, I challenge plausible deniability designers to `dd` a 6TB disk > with pseudorandom bytes, then try walking it across the U.S. border until it > gets searched. What could possibly go wrong? Should you be ordered to > decrypt it, the disk *could* be *plausibly* filled with pseudorandom bytes; > and you would not be committing the crime of lying to an officer, when you > truly state that in fact, it *is* filled with pseudorandom bytes.
It's very common for disks to be filled with pseudorandom data; this is not suspicious at all. For example: 1) An encrypted partition that is filled, and later reformatted, will be left full of random bytes. Even if you give border security your passphrase, the unused space in the encrypted partition will be random data. (an exception being most - but not all! - SSD's where TRIM has been used) 2) Modern drives (SSD and HD) often implement fast secure erasure with encryption, which means that the actual data stored to disk or FLASH is *always* encrypted. If such a drive is wiped, the encryption keys are replaced, which means whatever data was stored becomes random noise (the encrypted data is usually not authenticated). This also means that such drives can arrive from the factory filled with random noise. 3) Software disk encryption schemes have the same property: reformatting results in a drive filled with random noise. The latter is particularly interesting with LUKS, as you can do all kinds of things like erase the drive with luksErase, while keeping a backup of the LUKS header elsewhere. -- https://petertodd.org 'peter'[:-1]@petertodd.org
signature.asc
Description: Digital signature
_______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
