Re: pinentry problems
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 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 allowed." and it did that with every file in that
> folder.
Seems like a mixup of chmod and chown there, although make sure the user
is correct as well.
>>>
>>> yep, sorry, that should have been "chmod", not "chown" -- my mistake!
>>>
>>> --dkg
>>>
>> Ok, it did work with the chmod command.
>> Have you got any further ideas?
>
> remember to restart gpg-agent after doing that, gpgconf --kill gpg-agent
>
>
I did. This works fine as I asses that.
Now I'm still stuck with the pinentry problem.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: pinentry problems
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 '{}' ';'
> 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 allowed." and it did that with every file in that
folder.
>>>
>>> Seems like a mixup of chmod and chown there, although make sure the user
>>> is correct as well.
>>
>> yep, sorry, that should have been "chmod", not "chown" -- my mistake!
>>
>> --dkg
>>
> Ok, it did work with the chmod command.
> Have you got any further ideas?
remember to restart gpg-agent after doing that, gpgconf --kill gpg-agent
--
Kristian Fiskerstrand
Blog: https://blog.sumptuouscapital.com
Twitter: @krifisk
Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
Acta est fabula
So ends the story
signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: pinentry problems
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 '{}' ';'
>>> didn't work.
>>> The terminal responded: "chown: The owner of data XXX is going to be
>>> changed. This is not allowed." and it did that with every file in that
>>> folder.
>>
>> Seems like a mixup of chmod and chown there, although make sure the user
>> is correct as well.
>
> yep, sorry, that should have been "chmod", not "chown" -- my mistake!
>
> --dkg
>
Ok, it did work with the chmod command.
Have you got any further ideas?
Paul
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: pinentry problems
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 '{}' ';'
>>> didn't work.
>>> The terminal responded: "chown: The owner of data XXX is going to be
>>> changed. This is not allowed." and it did that with every file in that
>>> folder.
>>
>> Seems like a mixup of chmod and chown there, although make sure the user
>> is correct as well.
>
> yep, sorry, that should have been "chmod", not "chown" -- my mistake!
>
> --dkg
>
Ok, it did work with the chmod command.
Have you got any further ideas?
Paul
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: gpgme_op_verify regression with gnupg 2.2.6?
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. -- Kristian Fiskerstrand Blog: https://blog.sumptuouscapital.com Twitter: @krifisk Public OpenPGP keyblock at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 "History doesn't repeat itself, but it does rhyme." (Mark Twain) signature.asc Description: OpenPGP digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: pinentry problems
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: "chown: The owner of data XXX is going to be
>> changed. This is not allowed." and it did that with every file in that
>> folder.
>
> Seems like a mixup of chmod and chown there, although make sure the user
> is correct as well.
yep, sorry, that should have been "chmod", not "chown" -- my mistake!
--dkg
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Speedo build error on GnuPG 2.2.6
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; > 6fbe2ddbaf5123ae444c95fdf8da67840f794c76$178 > > But gnupg21_ver seems to be deleted by this commit: > https://dev.gnupg.org/rD2094fc1631aca2659732e0b28e03012e2dc67127 I noticed that, too and fixed it in the stable branch (should be merged into master soon) https://dev.gnupg.org/rG327fece0aed2c9974659c72304f9fd1f461d460c Can you try to cherry pick that commit and see if it works? When building from GIT I also use SELFCHECK=0 to avoid version problems. What works for me is: /usr/bin/make -f build-aux/speedo.mk native \ INSTALL_PREFIX=/opt/gnupg SELFCHECK=0 That works for me. Best Regards, Andre -- Andre Heinecke | ++49-541-335083-262 | http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
speedo build error on 2.2.6
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 2018 UTC using RSA key ID --- gpgv: Good signature from "---" GnuPG 2.1 version missing in swdb.lst! /gnupg-2.2.6/build-aux/speedo.mk:278: *** Error getting GnuPG software version database. Stop. make[1]: Leaving directory '/gnupg-2.2.6' build-aux/speedo.mk:73: recipe for target 'native' failed make: *** [native] Error 2 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;6fbe2ddbaf5123ae444c95fdf8da67840f794c76$178 But gnupg21_ver seems to be deleted by this commit: https://dev.gnupg.org/rD2094fc1631aca2659732e0b28e03012e2dc67127 Regards, Yuki ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Speedo build error on GnuPG 2.2.6
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 2018 UTC using RSA key ID --- gpgv: Good signature from "---" GnuPG 2.1 version missing in swdb.lst! /gnupg-2.2.6/build-aux/speedo.mk:278: *** Error getting GnuPG software version database. Stop. make[1]: Leaving directory '/gnupg-2.2.6' build-aux/speedo.mk:73: recipe for target 'native' failed make: *** [native] Error 2 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; 6fbe2ddbaf5123ae444c95fdf8da67840f794c76$178 But gnupg21_ver seems to be deleted by this commit: https://dev.gnupg.org/rD2094fc1631aca2659732e0b28e03012e2dc67127 Regards, Yuki ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: pinentry problems
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 allowed." and it did that with every file in that
> folder.
Seems like a mixup of chmod and chown there, although make sure the user
is correct as well.
--
Kristian Fiskerstrand
Blog: https://blog.sumptuouscapital.com
Twitter: @krifisk
Public OpenPGP keyblock at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
"History repeats itself; historians repeat each other"
(Philip Guedalla)
signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: pinentry problems
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 ~/.gnupg/*
>>
>> from here: https://superuser.com/a/954639
>
> this doesn't look right to me.
>
> in particular, it's going to remove the "execute/traverse" permission on
> ~/.gnupg/private-keys-v1.d/, which means that gpg-agent isn't going to
> be able to get a list of all available secret keys.
>
> Probably, you want to do the following (as your normal user account):
>
> find ~/.gnupg -type d -exec chown 0700 '{}' ';'
> find ~/.gnupg -type f -exec chown 0600 '{}' ';'
>
> if you do that, then you should be able to see some files whose names
> end in ".key" in ~/.gnupg/private-keys-v1.d/, like so:
>
> ls -l ~/.gnupg/private-keys-v1.d/*.key
>
> if that's the case, then i recommend you ask your running gpg-agent to
> shut down because it's probably confused:
>
>gpgconf --kill gpg-agent
>
> a new gpg-agent should start up again afterward as soon as you need it.
> you can also try to see which secret keys are available like this:
>
>gpg --with-keygrip --list-secret-keys
>
> You should see that the keygrips listed match the files found in the
> "ls" output above.
>
> If that doesn't work for you, please report back and we'll try to debug
> further :)
>
> --dkg
>
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 allowed." and it did that with every file in that
folder.
The rest of the commands are finde and I see the secret keys and the
matching keygrips.
Paul
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
