On Saturday 03 January 2009, Chris wrote: > On Saturday 03 January 2009 11:07:47 Chris wrote: > > On Saturday 03 January 2009 09:21:58 Ingo Klöcker wrote: > > > > Starting as root worked > > > > > > Please don't do anything as root. It is totally unnecessary, very > > > dangerous and will only lead to confusion. > > > > I only 'tried' it as root since you had entered #gpg-agent --daemon > > which on my box is the root login. I stopped the root process and > > started it as 'chris' where it is running now.
Okay. > > > > so I then entered eval "$(gpg-agent > > > > --daemon)" and it now shows as a running process. Stopped and > > > > restarted Kmail, I did not get the warning that gpg-agent > > > > wasn't running this time which is good so I tried adding my > > > > signing key to the identies configuration. The 'fetchnig keys' > > > > scroll bar still just moves back and forth as if it can't find > > > > anything. I noticed that kgpg was running as 'chris' so I > > > > stopped the root gpg-agent and started as 'chris', I saw this: > > > > > > > > [ch...@localhost ~]$ eval "$(gpg-agent --daemon)" > > > > can't connect to `/home/chris/.gnupg/log-socket': No such file > > > > or directory > > > > > > > > gpg-agent shows to be running under processes though. > > > > > > > > When running kmail as root and just setting up a quick identity > > > > when trying to fetch the keys there is no acitivty at all in > > > > the scrollbar > > > > > > You started gpg-agent as chris and kmail as root? This cannot > > > work. See what I meant above with "It [...] will only lead to > > > confusion."? > > > > Again, I just did a quick check while gpg-agent was running as root > > to see if kmail started as root would pickup the key. Kmail and > > gpg-agent are running as 'chris' and neither are running as root. > > > > > What happens if you do the following as 'chris' (e.g. in > > > Konsole)? [ch...@localhost ~]$ killall gpg-agent > > > [ch...@localhost ~]$ killall kmail > > > [ch...@localhost ~]$ eval "$(gpg-agent --daemon)" > > > [ch...@localhost ~]$ kmail > > > > [ch...@localhost ~]$ killall gpg-agent > > [ch...@localhost ~]$ killall kmail > > [ch...@localhost ~]$ eval "$(gpg-agent --daemon)" > > can't connect to `/home/chris/.gnupg/log-socket': No such file or > > directory > > [ch...@localhost ~]$ kmail > > > > Apologies for the confusion > > > > Chris > > One other note, after logging out and back in again to the system a > warning that gpg-agent is not running is displayed however looking at > running processes shows that it is under 'chris'. The warning is a bit misleading. It should read "gpg-agent cannot be connected to" or similar. In order to connect to gpg-agent the application needs to know the "channel" to use for talking to gpg-agent. This "channel" (a Unix socket) is announced with the environment variable $GPG_AGENT_INFO. Therefore only applications running in the same environment as gpg-agent can talk to gpg-agent. Did you add the file start-gpg-agent.sh to ~/.kde/env (or ~/.kde4/env or whatever folder is used for KDE 4 by Mandriva 2009)? As I wrote in my first reply this will ensure that gpg-agent is started whenever KDE is started, i.e. whenever you log in. Moreover, it ensures that all applications started from KDE are running in the same environment as gpg-agent and thus should be able to talk to gpg-agent. Regards, Ingo
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
