linux-kernel - Re: How to blacklist a usb_storage device from attach to the usb

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: <20123.60660.896589.761967@elektron.ikp.physik.tu-darmstadt.de>
Date:	Mon, 17 Oct 2011 10:53:08 +0200
From:	Uwe Bonnes <bon@...ktron.ikp.physik.tu-darmstadt.de>
To:	linux-kernel@...r.kernel.org
Subject: Re: How to blacklist a usb_storage device from attach to the
   usb_storage module

>>>>> "Uwe" == Uwe Bonnes <bon@...ktron.ikp.physik.tu-darmstadt.de> writes:

    Uwe> Hello, The STxxDiscovery Modules are affordable small boards with
...
    Uwe> blacklisting there will need time to propagate to the kernel tree
    Uwe> and back to the distributions. So a way to runtime blacklist is
    Uwe> needed too.

To answer my own question, at least partial, with and udev Rule like
SUBSYSTEM=="usb", ACTION=="add", ATTRS{idVendor}=="0483", \
ATTRS{idProduct}=="3744", DRIVER=="usb-storage", \
RUN+="/bin/sh -c 'echo -n %k> %S%p/driver/unbind'"

as the first rule for the device, the device still binds to the driver but
as first action is unbinded.

Should such a device still be blacklisted in the kernel somehow?

-- 
Uwe Bonnes                bon@...ktron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
--
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/