All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: permissions: udev vs. pam_devperm.so
Date: Tue, 26 Oct 2004 14:47:32 +0000	[thread overview]
Message-ID: <20041026144732.GB2009@vrfy.org> (raw)
In-Reply-To: <417DF0A8.2060108@bio.ifi.lmu.de>

On Tue, Oct 26, 2004 at 03:49:12PM +0200, Frank Steiner wrote:
> Kay Sievers wrote
> 
> 
> >I don't think that this will work, as there should be a remove event
> >before you get a new add event and the node will be deleted and recreated
> >without anything to preserve. You may check the inode number, it should
> >have changed.
> 
> Ok, I see... So, do you think it was possible to make sth. similar to
> pam_devperm? E.g., my /etc/logindevperms has a line
> 
>   :0 0600 /dev/dvd:/dev/dvd1:/dev/dvd2:/dev/dvd3
> 
> When a user logs in with kdm (/etc/pam.d/kdm defines using pam_devperm.so),
> /dev/dvd (i.e., the device this link points to, here: /dev/hdc) will be
> set to 600 and the user logging in will be the owner.
> Makes sense for a certain set of devices.
> 
> Maybe udev could use pam_devperm in a similar way? Or allow a special
> keyword like "console" as owner in the permissions file, setting the
> user who owns the console as owner of the device (and the default if
> no such user currently exists)? This way, devices added after the user
> has logged in, could be assigned to the locally logged-in user, too.

The problem is that every distribution has its own concept of "local" or
"console" users, so the best thing seems to call a distribution specific
permission-restore-script from dev.d/.

If this will not work for you, let us know and we will figure something
out.

Thanks,
Kay


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2004-10-26 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26  6:37 permissions: udev vs. pam_devperm.so Frank Steiner
2004-10-26 12:25 ` Kay Sievers
2004-10-26 12:30 ` Frank Steiner
2004-10-26 13:16 ` Kay Sievers
2004-10-26 13:20 ` Frank Steiner
2004-10-26 13:49 ` Frank Steiner
2004-10-26 14:47 ` Kay Sievers [this message]
2004-10-26 14:57 ` Kay Sievers
2004-10-27  0:02 ` Kay Sievers
2004-10-27  5:59 ` Frank Steiner

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=20041026144732.GB2009@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --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 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.