[wellylug] gpg: signing failed: secret key,not,available

[Tim]

On Wed, 2008-10-15 at 17:10 +1300, Adam Bogacki wrote:

> Also, I get the following ..
> 
> > Tohunga:~/.gnupg# ls -la
> > total 40
> > drwx------  2 root root 4096 2008-10-15 16:57 .
> > drwxrwx--- 82 root root 4096 2008-10-15 17:00 ..
> > -rw-------  1 root root   51 2008-10-15 15:18 gpg.conf
> > -rw-------  1 root root 7704 2008-10-04 17:52 pubring.gpg
> > -rw-------  1 root root 7704 2008-10-04 17:52 pubring.gpg~
> > -rw-------  1 root root  600 2008-10-04 18:05 random_seed
> > -rw-------  1 root root 1315 2008-10-04 17:52 secring.gpg
> > -rw-------  1 root root 1280 2008-10-04 17:52 trustdb.gpg
> .. and
> 
> > Tohunga:/home/adam/.gnupg# ls -la
> > total 48
> > drwx------   2 adam adam  4096 2008-10-15 17:00 .
> > drwxrwx--- 195 adam adam 12288 2008-10-15 16:32 ..
> > -rw-------   1 adam adam   130 2008-10-15 15:36 gpg.conf
> > -rw-------   1 adam adam 11980 2008-10-05 12:24 pubring.gpg
> > -rw-------   1 adam adam 11980 2008-10-05 12:24 pubring.gpg~
> > -rw-------   1 adam adam     0 2007-03-09 19:23 secring.gpg
> > -rw-------   1 adam adam  1200 2008-10-05 12:24 trustdb.gpg
> .. which in my home directory shows an empty 'secring.gpg' file,
> although it has 1315 bytes in ~/.gnupg .. possibly explaining why it
> tells me that
> "gpg: signing failed: secret key not available" when I use a program
> in /home/adam ..


The 1315 byte file is in ~root/.gnupg, which is not the same directory
as ~adam/.gnupg.

The behaviour you are seeing is consistent with the program
in /home/adam running as user adam, rather than as root:
- ROOT has a secret key, and can sign things
- ADAM does NOT have a secret key, so cannot sign things

Is that intended?

I would expect each account to have its own set of secret keys (after
all, adam at Tohunga is a different entity than root at Tohunga)


Tim