linux-kernel - Re: [ebeam PATCH v2 1/2] hid: Blacklist eBeam devices

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:	Thu, 11 Oct 2012 00:01:13 +0200
From:	Yann Cantin <yann.cantin@...oste.net>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
CC:	Jiri Kosina <jkosina@...e.cz>, linux-input@...r.kernel.org,
	linux-usb@...r.kernel.org, gregkh@...uxfoundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [ebeam PATCH v2 1/2] hid: Blacklist eBeam devices

Hi,

Le 10/10/2012 18:37, Dmitry Torokhov a écrit :
> Is the device usable at all with generic HID driver? If it isn't then
> maybe we should blacklist it unconditionally?

Without the libusb based proprietary stack, the device is unusable under linux.

If i correctly understand, libusb need a driver to be present in the first place,
(even a useless generic-usb) to be able to grab the device. If we unconditionally
blacklist the device and the ebeam driver isn't loaded (not compiled for example), no way
for libusb (and the stack) to handle the device.

As stated before, i'm not comfortable with the risk of breaking other hypothetical support,
even proprietary.

-- 
Yann Cantin
A4FEB47F
--
--
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/