linux-kernel - Restricting CDC-ACM 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-next>] [day] [month] [year] [list]

Message-ID: <39877.198.169.188.225.1187733834.squirrel@myweb.msoe.edu>
Date:	Tue, 21 Aug 2007 17:03:54 -0500 (CDT)
From:	"Nate" <stoddarn@...e.edu>
To:	linux-kernel@...r.kernel.org
Subject: Restricting CDC-ACM devices

I would like to use the cdc-acm driver in the Linux kernel (2.6.22-rc1),
but restrict the access to only my VID/PID devices.  Is there an easy way
to do with without modifying cdc-acm.c?

In a past prototype I made a simple wrapper driver for usb serial by
adding my VID/PID numbers to the wrapper driver's id_table.  Then when
that usb driver was accessed on connection, the driver just pointed to the
usb_serial_* functions (probe, disconnect, etc).  I tried to do the same
with the cdc-acm driver, but the cdc-acm driver's probe function was
called before my driver's probe.  I noticed that the cdc-amc driver will
attach when it detects the two CDC-ACM interfaces, so I removed the
cdc-acm driver with "make menuconfig".  This didn't work because the
cdc-acm functions I was attempting to call from my driver do not exist.

Thanks for the help,
-Nate

-
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/