netdev - Re: [PATCH] Adding blacklist support to the pegasus driver

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]

Message-ID: <alpine.DEB.1.10.0803252204180.3163@bender.nucleusys.com>
Date:	Tue, 25 Mar 2008 22:05:31 +0200 (EET)
From:	Petko Manolov <petkan@...leusys.com>
To:	Oliver Neukum <oliver@...kum.org>
cc:	Stefan Bader <stefan.bader@...onical.com>,
	linux-usb@...r.kernel.org, netdev@...r.kernel.org,
	petkan@...rs.sourceforge.net
Subject: Re: [PATCH] Adding blacklist support to the pegasus driver

On Mon, 24 Mar 2008, Oliver Neukum wrote:

> Am Montag 24 März 2008 schrieb Stefan Bader:
>> I have been working on a problem which arose from the fact that (at
>> least one vendor) some vendors use the same vendor and model number for
>> different pieces of hardware.
>
> That issue can be solved with using the correct macros for probing that
> include a device class check.

Can you show a driver that is already doing that.  I am sorry to be so 
lazy, but i can't help it... :-)


later,
Petko