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] [day] [month] [year] [list]

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

On 2009-06-14 17:54, Milan Broz wrote:
>> 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.
> 
> password prompt in Fedora is handled completely in userspace in initrd
> by plymouth, then it send password to cryptsetup.

Yes. I saw that in mkinitrd source...

> You did provide neither kernel log messages

The kernel is just booting up, messages scroll by fast, no strange stuff
appears as far as I can see.

> nor description of changes to
> your kernel config... 

I got the 2.6.29.4 .config, copied it into 2.6.30 tree and added ext4 as
fs and nfs4 server support. Nothing much in the area of where the
problem is?

> Try run it in text mode with full kernel log,

How to retrieve the log?

> also try enable some debug mode in plymouth and check exact error message.

Will have look into possibilties there.

> (Are you using mkinitrd from F11? Also see fedora bug 470740)

Indeed. This looks very much like it, although I use a normal PS/2
keyboard and I'll have to count the asterisks.
Thanks for this tip!!

Udo
--
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/