All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Waugh <twaugh@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: User-level USB device drivers, and permissions
Date: Fri, 5 Oct 2001 12:51:16 +0100	[thread overview]
Message-ID: <20011005125116.K7197@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]

I have a question regarding user-level USB device drivers.  The
project I'm thinking about is gphoto2.  I'm posting it here because at
least part of the solution lies in usbdevfs I think.

The problem is this:

How can a user-level USB device driver do its job while running as a
non-root 'console' user, with minimal (preferrably no) intervention
from the sysadmin?

By 'console' user, I am talking about the users that pam_console will
recognise as being on the console.

The closest solution at the moment seems to be: mount /proc/bus/usb
group-writable and group-owned by 'usb', and add users that can use
USB devices to group 'usb'.  This has the following problems:

- sysadmin needs to add any potential console users to the 'usb' group
  first,
- those users are then in the usb group even when not at the console.

An idea in my head is to have a pam module that, for console users,
mounts -tusbdevfs none /somewhere/usb-bus/$LOGNAME with user ownership
on login and dismounts it on logout, but I don't know if that is
feasible.

Does anyone know if this problem has already been solved, or else can
they think of a solution?

Thanks,
Tim.
*/

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2001-10-05 11:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05 11:51 Tim Waugh [this message]
2001-10-06  0:08 ` User-level USB device drivers, and permissions Oliver Neukum

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=20011005125116.K7197@redhat.com \
    --to=twaugh@redhat.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.