View Single Post
Estel's Avatar
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#1227
Originally Posted by yablacky View Post
Don't forget the device lock code which protects access to already mounted truecrypt data. Not sure if it can be more than 5 digits. Would need 155 digits for 512 bits. Do not assume brute force trying of device lock codes could not be automated by specialists.
Max is 8 digits - theoretical limit is 10, but when using it, it unlocks by *both* providing 10 digits, or first 8 only (!).

As for automating brute force of lock code, it's interesting idea. Lock code is trivial to break (DES), but only, if You have access to root filesystem, which *shouldn't* be possible without rebooting, if already presented with lock code prompt. When prompted, every 2 wrong attempts there is delay, that increases in 3th attempt, then disappear for next 2 attempts, and so goes on, in circle. Both delays are customizable (don't remember where, but it is easy to find it, IIRC).

Honestly, I can't think of any way, that would allow "3 letter agencies" and their specialists to retrieve lock code/unlock, without causing reboot (messing with flash storage content directly, without device in middle, should definitely cause reboot, and it's far from achievable, without de-soldering One NAND or cutting motherboard and doing extra-precise connections to certain paths itself, without harming other paths).

If anyone have sensible ideas, it's worth to discuss them in Truecrypt thread
---

yablacky, it's great to hear, that You've managed to move lock code prompt! May I ask, what are current pitfails about? Maybe someone will be able to help overcome them?

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 

The Following User Says Thank You to Estel For This Useful Post: