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

Message-ID: <47E7D266.8050500@canonical.com>
Date:	Mon, 24 Mar 2008 12:10:14 -0400
From:	Stefan Bader <stefan.bader@...onical.com>
To:	linux-usb@...r.kernel.org, netdev@...r.kernel.org
CC:	petkan@...rs.sourceforge.net
Subject: [PATCH] Adding blacklist support to the pegasus driver

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.
In this case the Belkin bluetooth dongle uses the same numbers as the
network adapter which causes machines to lock up as soon as the
bluetooth dongle gets inserted.
As far as I found there had been discussions about adding some sort of
blacklisting support to the pegasus module before but I have not found
any code doing so.
This is what the attached patch does. There is possibly much room for
improvement but at least it seems to work. Would it be possible to
include something like this in the mainline driver?
Please keep me cc'ed on replies, since I am not subscribed to the
mailing lists. Thanks.

Stefan

View attachment "0001-Add-blacklisting-support-to-pegasus-u.patch" of type "text/x-diff" (1785 bytes)