pinentry problems

Kristian Fiskerstrand kristian.fiskerstrand at sumptuouscapital.com
Tue Apr 17 11:11:22 CEST 2018


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)

-------------- 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/419d8e65/attachment-0001.sig>


More information about the Gnupg-users mailing list