From: Greg KH <greg@kroah.com>
To: Michael Weiser <michael@weiser.dinsnail.net>
Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 021 release
Date: Wed, 3 Mar 2004 17:19:20 -0800 [thread overview]
Message-ID: <20040304011919.GA2207@kroah.com> (raw)
In-Reply-To: <20040303235629.GA80132@weiser.dinsnail.net>
On Thu, Mar 04, 2004 at 12:56:29AM +0100, Michael Weiser wrote:
> On Wed, Mar 03, 2004 at 07:15:00AM -0800, Greg KH wrote:
> > > > Major changes from the 019 version:
> > > > - new variable $local for the udev.permission file allows
> > > > permissions to be set for the currently logged in user.
> > > Yay, just the other day I thought that might be a nice feature in
> > > concert with RedHat's/Fedora's pam_console module. Am I right in
> > > assuming that the current utmp based code will give the file to the user
> > > that most recently logged into the local console? This could cause some
> > > confusion with the pam_console-method which gives files to the user that
> > > logged in *first* on a local console.
> > I don't know, care to test it out?
> Aye. It's even worse. The user logged into the lowest-numbered console
> will get owner of the newly created file when using $local.
>
> So if I log into tty2 and plug in my USB stick I will be owner of
> /dev/sda1. If another guy comes along, logs into tty1, unplugs my USB
> stick and replugs it, he'll be owner of /dev/sda1. But if I log out now,
> re-login on tty2 and replug the stick again, I won't get the owner of
> /dev/sda1 but the other guy again. This will certainly break things - at
> least on Fedora Core 1. Maybe it's different with other
> distributions/glibc/utmp variants/versions.
Ick, well you are describing a pretty pathalogical situation. I suspect
for 99.9% of the users who would use this option, it will work just
fine, as they only have 1 user on the system at a time.
So, if you have multiple users on the physical system, then don't use
$local :)
Feel free to send a update to the documentation that illustrates this
limitation of the feature.
thanks,
greg k-h
next prev parent reply other threads:[~2004-03-04 1:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 0:09 [ANNOUNCE] udev 021 release Greg KH
2004-03-03 0:25 ` Greg KH
2004-03-03 9:56 ` Michael Weiser
2004-03-03 12:22 ` Ed Tomlinson
2004-03-03 15:14 ` Greg KH
2004-03-03 19:28 ` David Brownell
2004-03-03 22:53 ` Michael Weiser
2004-03-04 1:25 ` Greg KH
2004-03-04 3:58 ` Bill Nottingham
2004-03-04 18:26 ` Greg KH
2004-03-04 11:30 ` Romano Giannetti
2004-03-04 1:22 ` Marco d'Itri
2004-03-04 1:28 ` Greg KH
2004-03-04 9:27 ` Michael Weiser
2004-03-03 15:15 ` Greg KH
2004-03-03 23:56 ` Michael Weiser
2004-03-04 1:19 ` Greg KH [this message]
2004-03-04 6:37 ` Dominik Kubla
2004-03-04 18:44 ` Greg KH
2004-03-05 7:22 ` Dominik Kubla
2004-03-10 22:53 ` Greg KH
2004-03-04 17:48 ` Martin Schlemmer
2004-03-04 18:46 ` Greg KH
2004-03-04 18:56 ` Martin Schlemmer
2004-03-10 12:56 ` Prakash K. Cheemplavam
2004-03-10 22:51 ` Greg KH
2004-03-10 23:17 ` Prakash K. Cheemplavam
2004-03-11 1:21 ` Greg KH
2004-03-13 9:34 ` Prakash K. Cheemplavam
[not found] <1vshj-2ou-9@gated-at.bofh.it>
[not found] ` <1vBuj-3YL-17@gated-at.bofh.it>
2004-03-03 13:51 ` Pascal Schmidt
[not found] <20040303153403.21649.81059.Mailman@linux.us.dell.com>
[not found] ` <4048D503.10808@mail.ru>
2004-03-09 8:19 ` Greg KH
2004-03-09 10:16 ` rihad
2004-03-09 13:43 ` Alex Goddard
2004-03-10 22:52 ` Greg KH
[not found] <fa.dbn18ei.1k46o3i@ifi.uio.no>
[not found] ` <fa.afjk56q.t0ulic@ifi.uio.no>
2004-03-10 13:02 ` walt
2004-03-10 21:01 ` Prakash K. Cheemplavam
[not found] <fa.fkf6pbs.vk4328@ifi.uio.no>
[not found] ` <fa.aj3o3v7.pgqn9l@ifi.uio.no>
2004-03-10 23:01 ` walt
2004-03-11 0:11 ` Prakash K. Cheemplavam
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=20040304011919.GA2207@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@weiser.dinsnail.net \
/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