linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Owen Taylor <otaylor@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Xpert]Re: User-level Tasks in Hotplug Scripts?
Date: Sun, 03 Feb 2002 17:43:04 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-101275823330636@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101272582331992@msgid-missing>


Dr Andrew C Aitchison <A.C.Aitchison@dpmms.cam.ac.uk> writes:

> On Sat, 2 Feb 2002, Jim Gettys wrote:
> 
> > OK, folks (both X and wm-spec-list folks, that is, that I've added to
> > this thread):
> > 
> > How do we want to solve this problem?
> > 
> > We need a secure, interoperable way for configuration scripts running
> > as root to pop up configuration GUI's on user's servers, and we need it soon
> > (yesterday), as hot-plug is now a reality on Linux systems....
> 
> Are you sure you want to do this ?
> Are you *absolutely* sure you want to enable this in the default installation ?
> 
> If the root script cannot open a popup on the display, maybe it is because
> the display is currently being used by someone who shouldn't have access 
> to the popup.
> If I have a stand-alone machine, sure I want a popup when I install a new 
> printer/camera/player/reader in the USB/Firewire/PCMCIA socket.
> However, if this is a classroom machine I might not wish to allow any user
> to just plug in their device and use it. If the root script pops up a 
> config on their window they have just acquired more priviledges than I 
> wish to give them.

There's no reason at all that the configuration GUI has to 
automatically have root privileges; I would tend to expect
something along the lines of:

 A new device "USB Magic Camera" has been detected.
 Please enter the root password to configure this
 device:
           ..............

                            [ Cancel ] [  OK  ]

Regards,
                                        Owen

_______________________________________________
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

  reply	other threads:[~2002-02-03 17:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-03  8:43 [Xpert]Re: User-level Tasks in Hotplug Scripts? Dr Andrew C Aitchison
2002-02-03 17:43 ` Owen Taylor [this message]
2002-02-03 19:06 ` Jim Gettys
2002-02-03 19:59 ` Christer Palm
2002-02-03 20:46 ` David Brownell
2002-02-03 21:13 ` David Brownell
2002-02-03 23:49 ` Christer Palm
2002-02-04  5:57 ` Owen Taylor
2002-02-04 15:15 ` Vladimir Dergachev
2002-02-04 23:17 ` Oliver Neukum
2002-02-05  1:22 ` Christer Palm
2002-02-05  1:54 ` David Brownell
2002-02-05  2:14 ` Christer Palm
2002-02-05  2:41 ` David Brownell
2002-02-05  4:49 ` Vladimir Dergachev
2002-02-05  7:53 ` Oliver Neukum
2002-02-05  8:47 ` Dr Andrew C Aitchison
2002-02-05  8:56 ` Oliver Neukum
2002-02-05 11:21 ` Christer Palm
2002-02-05 11:35 ` Oliver.Neukum
2002-02-05 15:19 ` Jim Gettys
2002-02-05 18:37 ` Jim Carter

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=marc-linux-hotplug-101275823330636@msgid-missing \
    --to=otaylor@redhat.com \
    --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).