> You can set your text console keyboard to ASCII mode using "kbd_mode -a"
> command and to UTF-8 mode using "kbd_mode -u" command. Issuing either of
> those commands before you run gpg, losetup or something that requires a
> passphrase, should fix it. For text console, that is. For X windows, those
> commands may screw your keyboard setting really badly (haven't tested).
kbd_mode -{u,a} in X-Window causes the bash-box to crash. New lines come up just as if you hold down the Enter button. This is no solution.
In the Alt+F1 console kbd_mode returns UTF-8 and can be set to ASCII mode with no errors. However, neither mode can be used to decrypt the rootkey made up in Knoppix.
Even more astonishing:
Decrypting old keys made up in SuSE 10/10.1 work with no problems! The only critical part is the boot process, before the SuSE system loads. So I can either use a key for SuSE or for booting.
> Different defaults, not necessarily messed up.
No, I disagree. Each version was filled with flaws and they do it on full purpose. Why lacks the setup routine still for an offer to install SuSE on encrypted loops? They still ask for paritions. No solutions, just flaws each time. Knoppix 5.01 DVD has loop-aes built-in, so it´s obviously not a real difficulty.
> And in Knoppix it says "ASCII", which uses different encoding scheme for
> all
> those öäåÖÄÅ or whatever characters.
Yes, I want those special characters.
> In text console, run "kbd_mode -a", and try again.
I´ll answer this in the next mail. Hopefully my box will survive the test.
--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
