On Mon, 5 Dec 2011 16:32, w...@gnupg.org said:
> gpg --verify-options pka-lookups,pka-trust-increase --verify
Well, you also need the options
--keyserver-options honor-pka-record,auto-key-retrieve
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesges
On Mon, 5 Dec 2011 15:30, gn...@lists.grepular.com said:
> I then tried verifying the output from the above command, by piping it
> into this, using a gpg homedir that didn't contain my key:
>
> gpg --verify-options pka-lookups --verify
You may want to use:
gpg --verify-op
g.org=mike.cardwell.nos...@grepular.com" --clearsign
I then tried verifying the output from the above command, by piping it
into this, using a gpg homedir that didn't contain my key:
gpg --verify-options pka-lookups --verify
The result:
gpg: Signature made Mon 05 Dec 2011 14:25:17
On Mon, 5 Dec 2011 13:26, gn...@lists.grepular.com said:
> verification, but if you don't have the key already, it doesn't know the
> UID associated with the key used to sign and therefore can't do the PKA
> lookup... Is there some additional command line option that I should be
Well, PKA requir
Can anyone explain to me the purpose of "--verify-options pka-lookups" ?
I have successfully used "--auto-key-locate pka" when encrypting
messages, but I can't see how to use "pka-lookups".
I assumed it would automatically lookup/download the key in order to do
On Wed, Apr 05, 2006 at 10:56:13AM -0400, John W. Moore III wrote:
> Throughout the 'snapshot' phase of 1.4.3 this ability was turned OFF by
> default. With the release of 1.4.3 stable and the availability of
> cross-certification and pka-lookup now widely available, will the
> features once defau
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Throughout the 'snapshot' phase of 1.4.3 this ability was turned OFF by
default. With the release of 1.4.3 stable and the availability of
cross-certification and pka-lookup now widely available, will the
features once defaulted to off be defaulted t
