From: jg@pa.dec.com (Jim Gettys)
To: linux-hotplug@vger.kernel.org
Subject: Re: User-level Tasks in Hotplug Scripts?
Date: Sat, 02 Feb 2002 22:12:34 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101268798120155@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101256895903801@msgid-missing>
-
> From: 520047054719-0001@t-online.de (Oliver Neukum)
> Date: Sat, 2 Feb 2002 23:02:11 +0100
> To: jg@pa.dec.com (Jim Gettys), David Brownell <david-b@pacbell.net>
> Cc: Ryan Shaw <ryan.shaw@stanfordalumni.org>,
> linux-hotplug-devel@lists.sourceforge.net, wm-spec-list@gnome.org,
> xpert@xfree86.org
> Subject: Re: User-level Tasks in Hotplug Scripts?
> -----
> On Saturday 02 February 2002 21:55, 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....
>
> Is there anything wrong with the simplistic approach of having a demon
> listening on a socket? If you want it generic, you have to use generic
> means of communication.
>
You don't want to pass out permission to access your X server to anyone
who happens to ask for it (if you do, you've compromized everything,
or go down into compartmentalized workstation hell, someplace where we
went 10 years ago and found fundamentally painful).
So the issue is fundamentally one of authenticating
the configuration GUI's process to the X server to allow connection.
The other issue is how to associate the correct X display server with the
hotplug event, so that the correct user is notified. As I pointed out,
this is not necessarily local to the machine where the hotplug occurred.
- Jim
_______________________________________________
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
next prev parent reply other threads:[~2002-02-02 22:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 13:09 User-level Tasks in Hotplug Scripts? Ryan Shaw
2002-02-01 23:58 ` David Brownell
2002-02-02 20:55 ` Jim Gettys
2002-02-02 22:02 ` Oliver Neukum
2002-02-02 22:12 ` Jim Gettys [this message]
2002-02-02 22:52 ` Oliver Neukum
2002-02-02 23:02 ` David Brownell
2002-02-03 0:58 ` Scott Cuyle Fritzinger
2002-02-03 8:36 ` Greg KH
2002-02-04 6:02 ` Dmitry Yu. Bolkhovityanov
2002-02-04 15:10 ` Jim Gettys
2002-02-04 19:28 ` Jim Carter
2002-02-05 3:32 ` David Brownell
2002-02-05 15:05 ` Ryan Shaw
2002-02-06 14:30 ` Marcus Harnisch
2002-02-06 14:54 ` Jim Gettys
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-101268798120155@msgid-missing \
--to=jg@pa.dec.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).