You are not logged in.
Message during boot:
Unlocking encrypted volumes: [BUSY] ^[[udisk1..crypttab contains a literal encryption key. This
^[[uok ^[[udisk2..crypttab contains a literal encryption key. This will stop working in the future.What should I do? I use several literal encryption keys to unlock several partitions during booting including root.
The problem is in that I use remote unlocking of the root partition with literal key I enter manually from keyboard. I replaces the encrypt hook with dropbear encryptssh in /etc/mkinitcpio.conf.
What can I do if in the future it will be replaced with key-file instead of literal one. It is inconvenient to use key-file for remote computer file encryption?
Offline
So atm you have the actual passphrases in your /etc/crypttab?
From a security perspective this is not exactly the way to go as you can imagine. I would either switch the keyfiles or set "ASK" in your crypttab so you get prompted for the password(s) during boot.
Burninate!
Offline
So atm you have the actual passphrases in your /etc/crypttab?
Yes, I store plain passwords in /etc/crypttab, because /etc/crypttab is on the encrypted root partition. Encrypted root partition is decrypting during boot after entering literal password over ssh through network. I don't see anything wrong with that. I can't be asked for passwords, because I boot computer remotely.
Last edited by ZeroLinux (2012-05-02 08:09:32)
Offline
Your best bet is to switch to keyfiles in that case.
PS: some additional info about it on this mailing list message.
Burninate!
Offline
If I do it how I will decrypt my root partition during boot remotely?
Offline
You don't have to change anything to how your root partition is decrypted. It's only after your root partition has been decrypted/mounted and your /etc/crypttab is read that you'll be wanting to switch to keyfiles.
Burninate!
Offline
Thanks, I'll try to make it.
Offline
[...]Encrypted root partition is decrypting during boot after entering literal password over ssh through network. I don't see anything wrong with that. I can't be asked for passwords, because I boot computer remotely.
Actually, that's a may be a security hole.
You sshd keys are unencrypted, therefore, someone with physical access to you computer, can copy them, and then do a MITM attack to get your passphrase when you unlock it remotely.
If I do it how I will decrypt my root partition during boot remotely?
You can configure a single partition so that it can be unlocked both with a keyfile and a passphrase.
Offline