Re: Arch Linux impacted by new defaults in 2.2.17

2019-07-13 Thread Markus Reichelt
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.

Re: Avoiding hardcoded paths when static-compiling

2019-07-13 Thread Patrick Brunschwig
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

Re: test

2019-07-13 Thread David
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).

Re: test

2019-07-13 Thread David
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. > >

Re: test

2019-07-13 Thread Stefan Claas via Gnupg-users
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.

Re: test

2019-07-13 Thread Stefan Claas via Gnupg-users
-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

Re: test

2019-07-13 Thread Stefan Claas via Gnupg-users
-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

Re: test

2019-07-13 Thread Stefan Claas via Gnupg-users
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 ___