pinentry problems

[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 '{}' ';'
>>>>>     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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180417/323f5a9a/attachment-0001.sig>