On Wed, 14 Mar 2007 15:12, [EMAIL PROTECTED] said:
> I realize now this one was an RTFM. Problem was, I expected this
> information in man gpgsm, not man gpg-agent...
Yeah, I should really write the setup chapter for the manual.
Salam-Shalom,
Werner
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I've extracted some Thawte and CAcert keys and certs from my browser and
imported them into gpgsm. ls -l ~/.gnupg/private-keys-v1.d/ lists the
three private keys that I imported, and all of the corresponding certs
show up in --list-keys:
$ gpgsm --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Neglected to mention that the aforementioned problem was in gpgsm from
gnupg-2.0.3, with it and its four dependencies at latest release
versions, freshly compiled this weekend.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> * Is there a user trustlist.txt that can be used instead, or do I need
> to edit trustlist.txt as root every time a change needs to be made?
I realize now this one was an RTFM. Problem was, I expected this
information in man gpgsm, not man gpg-ag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On the one hand, yes, it was a gpg-agent problem. It turned out that
seahorse-daemon was running and screwing up the whole thing.
- --list-secret-keys started working once I unset GPG_AGENT_INFO. It
still complained that there was no gpg-agent runn
On Tue, 13 Mar 2007 23:41, [EMAIL PROTECTED] said:
>
> $ gpgsm --list-secret-keys
> /home/psmay/.gnupg/pubring.kbx
>
> $
There might be a problem with the gpg-agent. Make sure that gpg-agent
is running and add
verbose
debug 1024
log-file /for/bar/agent.log
to gpg-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
(This message is a dupe of one sent earlier under the wrong address;
admins, please deny the previous version.)
I've extracted some Thawte and CAcert keys and certs from my browser and
imported them into gpgsm (from gnupg-2.0.3, with it and all of i
