Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx> wrote:
> My guess is that you created and encrypted your key file using some
> character encoding in X windows terminal, and the system console character
> encoding that is used to decrypt the key file at boot is different and
> incompatible.
Creating a new gpg keyfile and keymap from the console doesn`t result in a working boot-CD either.
dumpkeys >{X-window, console}.kmap for console and X-window:
blue:~ # md5sum *.kmap
0e7752d3ea6a81d04d9d40820c2464d7 X-window.kmap
4d7d18e67eb2997d14cdb11df55e1787 console.kmap
This states a lack in dumpkeys to deliver equal keymaps, right?
> That "dumpkeys >/iso/default.kmap" saves system console keyboard mappings.
> What happens is you switch to system console using CONTROL-ALT-F1 and
> create
> new key file using that keyboard mapping? Type CONTROL-ALT-F7 to get back
> to
> X windows.
X window terminal:
blue:~ # read x ; echo -n ${x} | od -Ax -tx1 -
123
000000 31 32 33
000003
blue:~ # read x ; echo -n ${x} | od -Ax -tx1 -
µ€ ²³X
000000 c2 b5 e2 82 ac 20 c2 b2 c2 b3 58
00000b
blue:~ # read x ; echo -n ${x} | od -Ax -tx1 -
µüöä@
000000 c2 b5 c3 bc c3 b6 c3 a4 40
000009
-------------------------------------------------
system console (ctrl+alt+F1):
blue:~ # read x ; echo -n ${x} | od -Ax -tx1 -
123
000000 31 32 33
000003
blue:~ # read x ; echo -n ${x} | od -Ax -tx1 -
µ€ ²³X
000000 c2 b5 c2 a4 20 c2 b2 c2 b3 58
00000a
blue:~ # read x ; echo -n ${x} | od -Ax -tx1 -
µüöä@
000000 c2 b5 c3 bc c3 b6 c3 a4 40
000009
This output show differences between console and X-window keymapping but I fail to interpret it truely. So, what might be a solution? Build gpg keys and boot-CD under Knoppix? Use loadkeys & default.kmap from SuSE 10.1? Can you give further instructions that may help to find a solution?
Regards,
Peter
--
"Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ...
Jetzt GMX ProMail testen: http://www.gmx.net/de/go/promail
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
