linux-kernel - Re: crypt issue with 2.6.30/gcc 4.4.0?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 14 Jun 2009 17:54:10 +0200
From:	Milan Broz <mbroz@...hat.com>
To:	Udo van den Heuvel <udovdh@...all.nl>
CC:	linux-kernel@...r.kernel.org
Subject: Re: crypt issue with 2.6.30/gcc 4.4.0?

Udo van den Heuvel wrote:
> I am having trouble decrypting my dm-crypted disks with 2.6.30. 2.6.29.4
> works fine with the same encrypted disks.
> I've been upgrading to Fedora 11 in the past few days so now GCC 4.4.0
> is the compiler, that may (also) be a factor.
> 
> On 2.6.92.4 I see the encryption password prompt being buried by a lot
> of USB-messages from connected gear. I can 'blindly' type my password
> and asterisks appear for each letter. At the end of the password I press
> Enter; a complaint about the partition table for md1 is displayed and
> booting continues.
> With 2.6.30 I see the Password prompt being repeated, after all the USB
> messages, as soon as I press the first letter of the password. Each time
> the password is entered it is not accepted and a new Password: prompt is
> printed up to a total of three tries.

Hi,
password prompt in Fedora is handled completely in userspace in initrd
by plymouth, then it send password to cryptsetup.

You did provide neither kernel log messages nor description of changes to
your kernel config... Try run it in text mode with full kernel log,
also try enable some debug mode in plymouth and check exact error message.

Anyway, the problem is probably in some misconfiguration in you initrd
(like missing kernel module - some new module maybe needed now for your config,
bad order of module loading, device name changes of underlying device, maybe some
timing problem initialization of USB keyboard etc.) and not in kernel itself.
(Are you using mkinitrd from F11? Also see fedora bug 470740)

Milan
--
mbroz@...hat.com

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/