Would be nice to lock (password protect) the config or a button/command.
As I use some autologins to misc TrueCrypt-drives and other things it would be great, if no one would be able to find out passes when just looking into configuration mode.
Would be nice to lock (password protect) the config or a button/command.
As I use some autologins to misc TrueCrypt-drives and other things it would be great, if no one would be able to find out passes when just looking into configuration mode.
Why not make the button ask you for the TrueCrypt password?
If you're typing a password at all to run the button, it might as well be the password for the actual thing, rather than a password for the button. Then you don't have to store any password at all.
Alternatively, check out a tool like Keepass Password Safe which you can configure to auto-type passwords when things like TrueCrypt prompt you for them. You can set it so that you push a hotkey when prompted, and then you type in a "master password", and it will look up the appropriate password for the prompt and type it in for you.
(That way you can have a very long and secure password on the container or network resource while having something easier to type on the password database, with the assumption that someone is more likely to try to brute-force the network resource than the password database which they shouldn't be able to get to in the first place.)
It works very well:
"X:\Programs\TrueCrypt\TrueCrypt.exe" /q /v /lp /m rm Y:\cryptedfile
This will bring up the password login directly. Installation drive X & cryptfile located on Y are examples.