Re: pinentry problems

2018-04-17 Thread Paul H. Hentze
On 17.04.2018 00:49, Daniel Kahn Gillmor wrote: > On Tue 2018-04-17 00:04:11 +0200, Paul H. Hentze wrote: >>> gpg: WARNING: unsafe permissions on homedir '/home/giraffenhorde/.gnupg' >> >> So I fixed that with >> >>> chown -R "$USER:$(id -gn)" ~/.gnupg >>> chmod 700 ~/.gnupg >>> chmod 600

Re: pinentry problems

2018-04-17 Thread Kristian Fiskerstrand
On 04/17/2018 10:52 AM, Paul H. Hentze wrote: > Actually those commands >> find ~/.gnupg -type d -exec chown 0700 '{}' ';' >> find ~/.gnupg -type f -exec chown 0600 '{}' ';' > didn't work. > The terminal responded: "chown: The owner of data XXX is going to be > changed. This is not

speedo build error on 2.2.6

2018-04-17 Thread Yuki Ito
Hi, I've tried speedo build on GnuPG 2.2.6, but I've got an error like this: $ make -f build-aux/speedo.mk native make -f /gnupg-2.2.6/build-aux/speedo.mk UPD_SWDB=1 TARGETOS=native WHAT=release WITH_GUI=0 all make[1]: Entering directory '/gnupg-2.2.6' gpgv: Signature made Fri Apr 13 08:47:30

Speedo build error on GnuPG 2.2.6

2018-04-17 Thread Yuki Ito
Hi, I've tried speedo build on GnuPG 2.2.6, but I've got an error like this: $ make -f build-aux/speedo.mk native make -f /gnupg-2.2.6/build-aux/speedo.mk UPD_SWDB=1 TARGETOS=native WHAT=release WITH_GUI=0 all make[1]: Entering directory '/gnupg-2.2.6' gpgv: Signature made Fri Apr 13 08:47:30

Re: Speedo build error on GnuPG 2.2.6

2018-04-17 Thread Andre Heinecke
Hi, thanks for trying out up to date GnuPG :-) On Tuesday, April 17, 2018 5:55:26 PM CEST Yuki Ito wrote: > The build script verifies GnuPG version based on gnupg21_ver in swdb.lst: > https://dev.gnupg.org/source/gnupg/browse/master/build-aux/getswdb.sh; >

Re: pinentry problems

2018-04-17 Thread Daniel Kahn Gillmor
On Tue 2018-04-17 11:11:22 +0200, Kristian Fiskerstrand wrote: > On 04/17/2018 10:52 AM, Paul H. Hentze wrote: >> Actually those commands >>> find ~/.gnupg -type d -exec chown 0700 '{}' ';' >>> find ~/.gnupg -type f -exec chown 0600 '{}' ';' >> didn't work. >> The terminal responded:

Re: gpgme_op_verify regression with gnupg 2.2.6?

2018-04-17 Thread Kristian Fiskerstrand
On 04/16/2018 02:14 PM, Werner Koch wrote: >> Could gnupg 2.2.7 detect if gpgme is installed at all and if it is, >> make sure it's at least version 1.10.1 / 1.11.0? > :-) - No. Speaking for Gentoo we can do this on distribution level by adding a blocker on the lower version if needed. --

Re: pinentry problems

2018-04-17 Thread Paul H. Hentze
On 17.04.2018 17:48, Daniel Kahn Gillmor wrote: > On Tue 2018-04-17 11:11:22 +0200, Kristian Fiskerstrand wrote: >> On 04/17/2018 10:52 AM, Paul H. Hentze wrote: >>> Actually those commands find ~/.gnupg -type d -exec chown 0700 '{}' ';' find ~/.gnupg -type f -exec chown 0600

Re: pinentry problems

2018-04-17 Thread Paul H. Hentze
On 17.04.2018 17:48, Daniel Kahn Gillmor wrote: > On Tue 2018-04-17 11:11:22 +0200, Kristian Fiskerstrand wrote: >> On 04/17/2018 10:52 AM, Paul H. Hentze wrote: >>> Actually those commands find ~/.gnupg -type d -exec chown 0700 '{}' ';' find ~/.gnupg -type f -exec chown 0600

Re: pinentry problems

2018-04-17 Thread Kristian Fiskerstrand
On 04/17/2018 10:48 PM, Paul H. Hentze wrote: > > > On 17.04.2018 17:48, Daniel Kahn Gillmor wrote: >> On Tue 2018-04-17 11:11:22 +0200, Kristian Fiskerstrand wrote: >>> On 04/17/2018 10:52 AM, Paul H. Hentze wrote: Actually those commands > find ~/.gnupg -type d -exec chown 0700

Re: pinentry problems

2018-04-17 Thread Paul H. Hentze
On 17.04.2018 22:50, Kristian Fiskerstrand wrote: > On 04/17/2018 10:48 PM, Paul H. Hentze wrote: >> >> >> On 17.04.2018 17:48, Daniel Kahn Gillmor wrote: >>> On Tue 2018-04-17 11:11:22 +0200, Kristian Fiskerstrand wrote: On 04/17/2018 10:52 AM, Paul H. Hentze wrote: > Actually those