Re: Session Management Proposal
- From: George <jirka 5z com>
- To: Oswald Buddenhagen <ossi kde org>, xdg-list freedesktop org, Ray Strode <halfline hawaii rr com>, Mark Finlay <sisob tuxfamily org>, gnome-hackers gnome org, hp redhat com, mark skynet ie, ettrich kde org
- Subject: Re: Session Management Proposal
- Date: Sat, 3 Jan 2004 09:50:19 -0800
On Tue, Dec 30, 2003 at 01:23:53AM +0100, Oswald Buddenhagen wrote:
> > So I think with something like consolehelper this problem is
> > already solved.
> >
> if you'd explain what consolehelper does exactly ... :}
consolehelper is this thing (apparently redhat specific I think) that can
basically run certain binaries under root privilages if you are on the
console. You can either require the root password or not. This is the way
that GDM currently sets up gdmsetup as well to ask for the root password
when run as a user.
> > A common thing would be nice, but really so far there are 2 different
> > implementations GDM (only in the CVS version though) and KDM and so I don't
> > think it's a huge issue anyway - just implement both so far. GDM allows
> > querying which actions are available and that's really the only thing where
> > it differs from KDM. That's the only difference.
> >
> well, two protocols are one too much, as far as "standard" is concerned,
> no? ;)
> what kdm currently does is clearly insufficient for the features i'm
> planning, so i have to come up with something better anyway. i'm not sure
> whether i will just use/extend the gdm socket protocol; i'll have to
> investigate that (but you can expect some significant changes, if :).
>
> i'll try to write some half-assed spec for the dm-related part of all
> this, but if i'll be as fast as last time ... :}
I think the gdm protocol is semi decent in retrospect. There are several
things though:
1) get rid of the authentication bullshit, start one main socket say:
/tmp/.dm-sockets/main for the unauthenticated stuff and then
per-display sockets like /tmp/.dm-sockets/:0 for the stuff that
requires authentication (console authentication currently). That
way this can be done with unix permissions rather then the cookie
juggling.
2) There should be a way to query available 'commands' so that a client
can see what the DM can and can't do, and this will allow gdm and kdm
specific commands. Or dm-specific extended commands.
George
--
George <jirka 5z com>
I know not with what weapons World War III will be fought, but
World War IV will be fought with sticks and stones.
-- Albert Einstein
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]