[opensuse-security] Today kernel upgrade breaks crypto system!
nimrodel:~ # /etc/init.d/boot.crypto start Activating crypto devices using /etc/cryptotab ... /dev/disk/by-id/ata-ST3320620A_5QF2M56F-part15... failed It does not ask for password, it simply fails. There is no entry in logs. No clue :-/ nimrodel:~ # uname -a Linux nimrodel 2.6.25.16-0.1-pae #1 SMP 2008-08-21 00:34:25 +0200 i686 i686 i386 GNU/Linux nimrodel:~ # cat /proc/version Linux version 2.6.25.16-0.1-pae (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-08-21 00:34:25 +0200 nimrodel:~ # cat /etc/SuSE-release openSUSE 11.0 (i586) VERSION = 11.0 Where can I get the previous kernel to back-off just the last upgrade? -- Cheers, Carlos Robinson --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-09-11 at 21:49 +0200, Carlos E. R. wrote:
nimrodel:~ # /etc/init.d/boot.crypto start Activating crypto devices using /etc/cryptotab ... /dev/disk/by-id/ata-ST3320620A_5QF2M56F-part15... failed
It does not ask for password, it simply fails. There is no entry in logs. No clue :-/
Forget it. It wasn't the kernel, I solved the problem. Partly my thick-fingers, partly a bug in the script. I'll explain later. I need more sleep... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjJd8AACgkQtTMYHG2NR9WPCgCeMNmW6GM80in31K6qYL/+Z7jW LvIAn3brSvYP39/JWogPlqo1c7nASHX9 =u/aD -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-09-11 at 21:55 +0200, Carlos E. R. wrote:
nimrodel:~ # /etc/init.d/boot.crypto start Activating crypto devices using /etc/cryptotab ... /dev/disk/by-id/ata-ST3320620A_5QF2M56F-part15... failed
It does not ask for password, it simply fails. There is no entry in logs. No clue :-/
Forget it. It wasn't the kernel, I solved the problem. Partly my thick-fingers, partly a bug in the script. I'll explain later.
Explanation: When I rebooted, the init script prompted for my password. It seems I mistyped (or failed without prompt, I don't know), but it did not prompt to try again. In any case the boot process continued and I did not notice that the encrypted partition was not mounted. Then I manually mounted another encrypted partition, succeeding, and this one used the first loop device available, ie, loop0. It so happens that the first encrypted partition, defined in /etc/cryptotab, is hardcoded to use loop0... Thus when I first noticed that the first one was not mounted (when programs using it failed), and I tried to mount it again, it wasn't possible. I think there are two problems/bugs. 1) that the boot script failed to retry (I have to try again to make sure this is the case). 2) that later manually attempts failed to produce any message, even in dmesg, so that I had no clue why it was failing. Sorry for the false kernel warning. When I have the above clear I'll report to bugzilla. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjJjTQACgkQtTMYHG2NR9XfgQCfXaRZjFxBKfsEXFyVjalI7gS4 pGEAn3A9VVGNj9QHQQVrJ9yM5fxGw3gp =Xe4l -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org
participants (2)
-
Carlos E. R.
-
Carlos E. R.