Re: SuSE 10.2 and LOADNATIONALKEYB=1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Peter_22@xxxxxx wrote:
> > Your keyboard layout /boot/default.kmap (from knoppix) is not euro
> > compatible. When you press euro key, you get normal e.
> 
> This is all correct but it does not explain why passphrase is accepted at
> boot time and not in SuSE itself in case I use key and kmap from Knoppix.

To decrypt that key file that was created under Knoppix, you need to use
same character encoding as Knoppix, and same keyboard layout as Knoppix.
Complaining about being incompatible with something is meaningless unless
you also specify what you want to be compatible with. I know that old
version of Knoppix CD that I have defaults to ASCII keyboard mode, but I
still don't know what your version of Knoppix defaults to. Please tell me
what "kbd_mode" command in text console in your version of Knoppix says, and
what hex codes those problem characters output.

If you want to standardise on Knoppix defaults and want to operate with both
Knoppix and SUSE, then you have to convince SUSE installation to use Knoppix
keyboard layout and character encoding.

If you want to standardise on SUSE defaults and want to operate with both
Knoppix and SUSE, then you have to convince Knoppix live DVD to use SUSE
keyboard layout and character encoding.

Quote from your "Wed, 24 Jan 2007 12:14:13 +0100" posting:
> X window terminal:
> 000000 c2 b5 e2 82 ac 20 c2 b2 c2 b3 58
               ^^^^^^^^
> system console (ctrl+alt+F1):
> 000000 c2 b5 c2 a4 20 c2 b2 c2 b3 58
               ^^^^^
Above are supposed to be hex codes for same characters. Your SUSE X windows
and text console use different hex codes for euro symbol. The X windows hex
code (e2 82 ac) is true UTF-8 euro, but text console hex code (c2 a4) is
UTF-8 ¤.

My .fi text console keyboard layout outputs correct euro hex code (a4) for
ISO8859-15 encoding, but in UTF-8 mode it outputs wrong hex code (c2 a4),
same as yours.

> In the last hour I made up a boot stick with default.kmap and rootkey from
> within SuSE. I also used UTF8KEYBMODE=1 in initrd-conf file. I tried
> kernel parameter lang=de, too. No chance. Special characters are not
> accepted.

When does it fail? Does Knoppix mount fail, or does encrypted-root-initrd
mount fail?

Did you create that new default.kmap after fresh SUSE boot, or after you had
loaded that euro-incompatible-knoppix keyboard layout?

Did you encrypt your key file in X windows or text console? As is shown
above, X and text console output different hex codes for euro symbol when
keyboard is in UTF-8 mode. If you encrypted your key file in UTF-8 X windows
and attempted to decrypt it in UTF-8 encrypted-root-initrd boot text
console, then it is guaranteed to fail.

-- 
Jari Ruusu  1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9  DB 1D EB E3 24 0E A9 DD

-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/



[Index of Archives]     [Kernel]     [Linux Crypto]     [Gnu Crypto]     [Gnu Classpath]     [Netfilter]     [Bugtraq]
  Powered by Linux