From: Vladimir Dergachev <volodya@mindspring.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Xpert]Re: User-level Tasks in Hotplug Scripts?
Date: Mon, 04 Feb 2002 15:15:34 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101283580711339@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101272582331992@msgid-missing>
On Mon, 4 Feb 2002, Jim Gettys wrote:
> 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, if the user is logged in so is the rest of the user interface. Why
not have a monitoring program (like console) that watches the hotplug
events and invokes corresponding configuration program ? This would also
allow for various user environments to customize configuration tools to
match their look.
Vladimir Dergachev
>
>
> --
> Jim Gettys
> Cambridge Research Laboratory
> Compaq Computer Corporation
> jg@pa.dec.com
>
> _______________________________________________
> Xpert mailing list
> Xpert@XFree86.Org
> http://XFree86.Org/mailman/listinfo/xpert
>
_______________________________________________
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:15 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
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 [this message]
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-101283580711339@msgid-missing \
--to=volodya@mindspring.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 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.