Re: A comment on NetworkManager

[Jon Nettleton <jon nettleton gmail com>]

On Sat, 2006-05-13 at 11:09 -0400, Gene Heskett wrote:
> Garry T. Williams wrote:
> > [ I call BS on my post :-) ]
> > 
> > On Friday 12 May 2006 09:25, Garry Williams wrote:
> >> nm-applet will run in KDE just fine.  I added
> >>
> >>   /usr/libexec/gnome-settings-daemon
> >>   /usr/bin/gnome-keyring-daemon
> >>
> >> to my start-up list.
> > 
> > Unfortunately, this isn't going to get gnome-keyring-daemon hooked
> > into the KDE session.  The session does not have the keyring
> > environment variables, so nm-applet cannot contact it.
> > 
> > I didn't notice this because I did not try to use an encrypted network
> > after setting it up.
> > 
> > Here's how it should actually be done (from
> > http://bugzilla.ubuntu.com/show_bug.cgi?id=17463 ):
> > 
> > To get KDE to source the environment variables you need for clients to
> > be able to contact the gnome-keyring-daemon, add this script to your
> > ~/.kde/env directory:
> > 
> >     $ cat ~/.kde/env/start-custom.sh
> >     #!/bin/sh
> >     #
> > 
> >     # gnome keyring daemon
> >     # set env vars, much like ssh-agent
> >     eval `gnome-keyring-daemon`
> >     export GNOME_KEYRING_PID GNOME_KEYRING_SOCKET
> >     set | grep GNOME
> >     $
> > 
> > To make sure the gnome-keyring-daemon is shut down when you exit the
> > KDE session, add this script to your ~/.kde/shutdown directory:
> > 
> >     $ cat ~/.kde/shutdown/stop-custom.sh
> >     #!/bin/sh
> >     #
> > 
> >     # kill any gnome keyring daemons that we were using
> >     if [ -n "$GNOME_KEYRING_PID" ]; then
> >       echo killing gnome-keyring-damon $GNOME_KEYRING_PID
> >       kill $GNOME_KEYRING_PID
> >     fi
> >     $
> > 
> > Make both files executable and readable by your uid.
> > 
> > The startkde script will source executable scripts in the env
> > directory and will run scripts in the shutdown directory before
> > exiting the KDE session.
> > 
> > Do not add gnome-keyring-daemon to the KDE Autostart folder.
> > 
> Humm, but on FC5, there is not an env subdir in ~.kde.  Are we to create 
> this from whole cloth?
> 
> I've done this, but have not restarted X yet.  What are the expected 
> results considering that ATM my networking is working fine using network 
> to start it.
> 
Another option and a complete project plug is to use pam_keyring, which
will start the gnome-keyring-daemon from pam and setup the proper
environment variables.  The example config for gdm should work with any
pam configuration file.  You can check it out at
http://www.hekanetworks.com/pam_keyring

This won't work with Ubuntu right now because of the pam versions.  I am
getting ready to roll out a new version today or tomorrow that should
allow this to not be the case.

Hope this helps.