linux-kernel - Re: PROBLEM: 3.8.0-rc4 keyboard failure at boot

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:	Tue, 22 Jan 2013 18:22:42 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Brad Tilley <brad@....us>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: PROBLEM: 3.8.0-rc4 keyboard failure at boot

On Tue, 22 Jan 2013, Brad Tilley wrote:

> See attached. Two dmesgs from the same machine. One from 3.7.3, the 
> other from 3.8-rc4 (with a ps2 keyboard). USB keyboards on this machine 
> never work with 3.8, but always works with 3.7.
> 
> I used an old ps2 keyboard to enter the dm-crypt password. After that, 
> the boot process continues and the USB keyboard and mouse become active 
> and begin to work. However, USB keyboards do not work when the user is 
> prompted to enter the dm-crypt decryption password early in the boot 
> process. That's the primary issue.

Are you sure that HID modules are loaded at the time you are being asked 
for the dmcrypt password?

In the provided dmesg, I can see

[   17.106371] usb 2-1.2: New USB device found, idVendor=413c, idProduct=2106
[   17.106376] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   17.106380] usb 2-1.2: Product: Dell QuietKey Keyboard
[   17.106382] usb 2-1.2: Manufacturer: Dell
[   17.115713] input: Dell Dell QuietKey Keyboard as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input11
[   17.115968] hid-generic 0003:413C:2106.0002: input,hidraw1: USB HID v1.10 Keyboard [Dell Dell QuietKey Keyboard] onusb-0000:00:1d.0-1.2/input0

i.e. the keyboard gets properly autodeteted, but I have no idea whether 
this was before or after dm-crypt password prompt.

-- 
Jiri Kosina
SUSE Labs
--
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/