Stefan Claas via Gnupg-users [2019-07-14T06:55:53+02] wrote:
> My key is available via WKD or Hagrid.
I think you should add "--sender email@address" option so that your
signatures have information for WKD auto-key-retrieve method (and also
for TOFU statistics).
It is probably mail user agent's
David wrote:
> Hello Stefan,
>
> I mean to say - no keys were found :)
Maybe you have to adjust you settings.
My key is available via WKD or Hagrid.
(P.S. I forgot to insert a Message-ID,
so now threading is not correct.)
Regards
Stefn
___
Gnupg-us
On 13/07/2019 17:56, Stefan Claas via Gnupg-users wrote:
> Stefan Claas via Gnupg-users wrote:
>
> David wrote:
>
Just testing my e-,ails are getting through :)
But not signed :) no public key
David
>
> And a little reply, to see if my signature verifies properly.
>
> S
On 13/07/2019 17:45, Stefan Claas via Gnupg-users wrote:
> David wrote:
>
>> Just testing my e-,ails are getting through :)
>
>> But not signed :) no public key
>
>> David
>
> And a little reply, to see if my signature verifies properly.
>
> Step 1. Creating the reply in Notepad++ (offline).
>
Stefan Claas via Gnupg-users wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> David wrote:
>
> > Just testing my e-,ails are getting through :)
> >
> > But not signed :) no public key
> >
> > David
>
> And a little reply, to see if my signature verifies properly.
>
> Step 1. Cr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David wrote:
> Just testing my e-,ails are getting through :)
>
> But not signed :) no public key
>
> David
And a little reply, to see if my signature verifies properly.
Step 1. Creating the reply in Notepad++ (offline).
Step 2. Signing the mess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David wrote:
> Just testing my e-,ails are getting through :)
>
> But not signed :) no public key
>
> David
And a little reply, to see if my signature verifies properly.
Step 1. Creating the reply in Notepad++ (offline).
Step 2. Signing the mess
It's all about where they look for new/updated keys. There's folks
out there who use a WKD setup, as you mentioned, then there's some
who use a standalone (isolated, non-peering) SKS keyserver, etc.
I do not think reverting the patch that causes issues for them is a
smart move in the long run. [.
On 12.07.2019 21:21, Konstantin Ryabitsev wrote:
> Hi, all:
>
> I provide an RPM package called gnupg22-static for those who need to run
> newer versions of GnuPG on CentOS-7 environments (it's stuck on
> gnupg-2.0 there). For compilation, I use the convenient STATIC=1
> mechanism, but there's sti
