WKD auto-key-retrieve method
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 job to add "--sender" but maybe it is also fine to have that in gpg.conf file. -- /// OpenPGP key: 4E1055DC84E9DFF613D78557719D69D324539450 // https://keys.openpgp.org/search?q=tliko...@iki.fi / https://keybase.io/tlikonen https://github.com/tlikonen signature.asc Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: test
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-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: test
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. > > Step 1. Creating the reply in Notepad++ (offline). > Step 2. Signing the message (offline). > Step 3. Adding Headers (offline). > Step 4. Transfer with CoolTerm to online computer. > Step 5. Sending the message with openssl. > > Stefan > > Forgot the -quiet command in openssl, hence the error. > > Hope the second try is correct. > > Regards > Stefan > > ___ > Gnupg-users mailing list > Gnupg-users@gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-users > Hello Stefan, I mean to say - no keys were found :) David -- People Should Not Be Afraid Of Their Government - Their Government Should Be Afraid Of The People - When Injustice Becomes Law, REBELLION Becomes A DUTY! Join the Rebellion Today! https://gbenet.com signature.asc Description: OpenPGP digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: test
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). > Step 2. Signing the message (offline). > Step 3. Adding Headers (offline). > Step 4. Transfer with CoolTerm to online computer. > Step 5. Sending the message with openssl. > > Stefan > > > ___ > Gnupg-users mailing list > Gnupg-users@gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-users > Hello Stefan - I copied and pasted your key into a file - then imported it - but I could not find your public key in my list - you have a very small public key :) David -- People Should Not Be Afraid Of Their Government - Their Government Should Be Afraid Of The People - When Injustice Becomes Law, REBELLION Becomes A DUTY! Join the Rebellion Today! https://gbenet.com signature.asc Description: OpenPGP digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: test
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. Creating the reply in Notepad++ (offline). > Step 2. Signing the message (offline). > Step 3. Adding Headers (offline). > Step 4. Transfer with CoolTerm to online computer. > Step 5. Sending the message with openssl. > > Stefan > -BEGIN PGP SIGNATURE- > > iHUEARYIAB0WIQTJPiUt+ztNt+rrhGrY1GSzXhKrdwUCXSn/qwAKCRDY1GSzXhKr > dzwHAP4pjtOH72H4ZF/WXegsao/oVf7kAVKgl1zWAy2Ypg7PTgD8CtwPDxHoHxKq > FMf+JEVzkjuigzAhyRvE/1vbnkf5GwA= > =3gZ2 > -END PGP SIGNATURE- Forgot the -quiet command in openssl, hence the error. Hope the second try is correct. Regards Stefan ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: test
-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 message (offline). Step 3. Adding Headers (offline). Step 4. Transfer with CoolTerm to online computer. Step 5. Sending the message with openssl. Regards Stefan -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQTJPiUt+ztNt+rrhGrY1GSzXhKrdwUCXSn/qwAKCRDY1GSzXhKr dzwHAP4pjtOH72H4ZF/WXegsao/oVf7kAVKgl1zWAy2Ypg7PTgD8CtwPDxHoHxKq FMf+JEVzkjuigzAhyRvE/1vbnkf5GwA= =3gZ2 -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: test
-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 message (offline). Step 3. Adding Headers (offline). Step 4. Transfer with CoolTerm to online computer. Step 5. Sending the message with openssl. Stefan -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQTJPiUt+ztNt+rrhGrY1GSzXhKrdwUCXSn/qwAKCRDY1GSzXhKr dzwHAP4pjtOH72H4ZF/WXegsao/oVf7kAVKgl1zWAy2Ypg7PTgD8CtwPDxHoHxKq FMf+JEVzkjuigzAhyRvE/1vbnkf5GwA= =3gZ2 -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Arch Linux impacted by new defaults in 2.2.17
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. [...] Welcome to the mess of PKI. -- left blank, right bald ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Avoiding hardcoded paths when static-compiling
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 still the problem that all paths end up being
> hardcoded to the RPM buildroot environment.
>
> The full build command is:
> make -f build-aux/speedo.mk STATIC=1 CUSTOM_SWDB=1 INSTALL_PREFIX=.
> this-native
> In the RPM context, the INSTALL_PREFIX ends up being inside a buildroot
> location, like so:
>
> /builddir/build/BUILD/gnupg-2.2.17/
>
> However, the final installation of this will be in /opt/gnupg22, which
> means that if a binary needs to call another binary, it will try to
> execute /builddir/build/BUILD/gnupg-2.2.17/bin/foo (and fail).
>
> I can't set INSTALL_PREFIX=/opt/gnupg22, because that will make the RPM
> build fail (it cannot write outside of /builddir), so I need a way to
> tell the binaries during build time that their final install path will
> be different than the path used during build.
> I am able to use gpg and gpgv this way by setting agent-program and
> dirmngr-program config values, but trying to make this work with
> gpg-wks-server fails.
>
> Any pointers on how I can make this work without hardcoding bogus
> build-time paths?
I have the same situation for building gpgOSX. The solution is this:
./configure \
--with-pinentry-pgm=${TARGET_DIR}/bin/pinentry \
--with-agent-pgm=${TARGET_DIR}/bin/gpg-agent \
--with-scdaemon-pgm=${TARGET_DIR}/libexec/scdaemon \
--with-dirmngr-pgm=${TARGET_DIR}/bin/dirmngr \
--with-dirmngr-ldap-pgm=${TARGET_DIR}/libexec/dirmngr_ldap \
--with-protect-tool-pgm=${TARGET_DIR}/libexec/gpg-protect-tool \
etc.
-Patrick
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
