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