From: jg@pa.dec.com (Jim Gettys)
To: linux-hotplug@vger.kernel.org
Subject: Re: User-level Tasks in Hotplug Scripts?
Date: Mon, 04 Feb 2002 15:10:56 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101283551810342@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101256895903801@msgid-missing>
Fundamentally, we have no convention right now for any client (root or not)
to connect to an X server except on initiation of the user (unless
the user is silly enough to disable authentication entirely.
This is an generic X issue (how to delegate authorization to connect).
There is the xauth mechanism, not very secure, but no convention on its
use in these circumstances. There is also support for kerberos, which
is reasonably secure when used properly. And there is SSH, which has
never been integrated into X's world cleanly (and probably should be).
And there is Owen's scheme for
some sort of server process, but this presents much the same fundamental
security/authentication/authorization problem as well.
I don't have a preconcieved
notion of what the correct solution is; I'm not even very familiar with
the possibilities.
Certainly, I want no user intervention as much of the time as possible, but
we also need a hotplug design which allows for user intervention at the
time of first use in cases where it may be necessary. The hotplug script
design needs to allow for this, even if it is not the usual case.
And there is need to automatically run GUI based programs, even after
configuration (automatically downloading images off your camera, for
example).
Personally, I find it very frustrating to have to go looking for a configuration tool before I can use some hardware: this is not something
a (mere mortal) user knows in advance, and so don't believe the right thing
to do is necessarily nothing (though for much hardware this may be the correct
answer, it isn't for most casually used hardware).
We can certainly split this discussion to the different communities
if people think that is best, but I wanted to get the problem aired;
there is a problem for each community to mull over at the core of this
problem.
And someone who sends mail from an address "nogui" certainly has a strong
opinion on the topic, which may not be universal :-;.
- Jim
--
Jim Gettys
Cambridge Research Laboratory
Compaq Computer Corporation
jg@pa.dec.com
_______________________________________________
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-04 15:10 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
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 [this message]
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-101283551810342@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).