From: Peter Stuge <peter@stuge.se>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Libusb-devel] udev permissions for USB
Date: Wed, 27 Oct 2010 21:11:10 +0000 [thread overview]
Message-ID: <20101027211111.13771.qmail@stuge.se> (raw)
Kay Sievers wrote:
> >> Certain classes of USB devices like printers, fingerprint readers,
> >> scanners, webcams, ... get ACLs assigned for locally logged-in users
> >> only.
Which is good, but I think things could be even better.
> The commonly used groups are device-class based matches only. The
> udev-managed user ACLs are also class-based only, and not bus based.
> They are no unpredictable match like 'all pci devices'. For example,
> we must never grant access to a USB device which contains a
> usb-storage blockdevice.
Of course not. I don't think that was the intent of the request.
I do see value in special treatment for "usbfs-capable" interfaces;
ie. those that have either usbfs or no driver at all bound.
> You can just add such a udev rule to systems you administrate, if
> that's the behavior you expect and can be sure its not a security
> issue. The default udev installation does not
> suggest/recommend/support anything like this.
I think it could make sense for it to do so, not for all USB devices,
but for those that have no driver.
I'm not sure if it can actually be done reliably though. Maybe it's
enough to react on when an interface appears and/or loses it's
driver.
//Peter
next reply other threads:[~2010-10-27 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 21:11 Peter Stuge [this message]
2010-10-28 0:52 ` [Libusb-devel] udev permissions for USB Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101027211111.13771.qmail@stuge.se \
--to=peter@stuge.se \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).