Laszlo (Laca) Peter wrote:
On Tue, 2006-08-22 at 17:33 -0500, John Weekley wrote:
The GNOME session has been started via ssh-agent for quite a while.
This means that all GNOME apps are started as ssh clients and
therefore running ssh-add will affect all programs started from the
GNOME session.
An interesting approach, when was it introduced into SXCR?
It's been in gdm since around 2003, so those who use gdm as their
graphical login program have had this since S10. In snv_44 we moved
this piece of code from the gdm startup scripts to Xinitrc.jds
which is called by both gdm and dtlogin so now dtlogin users
also get this.
That's why I never saw it, I don't use gdm-login.
Seeing that in the process list was kind of a WTF? moment ;)
What's different in snv_46 is that dbus is now included so ssh-agent
now starts dbus-launch which will start gnome-session. When the
session ends, gnome-session exits and the dbus session daemon and
ssh-agent both exit with it.
The mechanics I understood, I guess I wasn't clear in my original
question. It's the rationale of the ssh-agent and dbus combination
(and the possibilities for use with other apps) that I was asking about.
Sorry, I misunderstood your question.
I don't think there is any interaction between dbus-daemon and ssh,
although it sounds like an interesting idea. The order they are started
is arbitrary, all we intended to do is start both at login and get rid
of them at the end of the session.
Oh, okay. I was under the impression that ssh-agent passed it's
environment info to dbus for other apps to use.
Since I posted the original question, I've been googling
a fair amount of information on the net about it, including a perl
Net::DBus module which looks interesting for a few applications I'm
working on.
Shame a prerequisite module, XML::Grove won't pass it's make tests on B46.
Laca
_______________________________________________
opensolaris-discuss mailing list
[email protected]
