On 18.04.2018 22:09, Daniel Kahn Gillmor wrote:
> can you explain the pinentry problem you're seeing? I'm afraid the bad
> ownership of your files was distracting from any other problems you were
> reporting.
>
> One simple way to test pinentry (without gpg or gpg-agent in the mix)
> is:
>
>
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,
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 '{}' ';'
>>>>
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 '{}' ';'
>>>>
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)&qu
Hey folks,
I'm kinda stuck here with a problem with pinentry and could use some help.
I described the hole problem in detail here:
https://sourceforge.net/p/enigmail/forum/support/thread/eedabe49/
For all who don't like links, I will copy it down below.
Patrick Brunschwig already asked some
test
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
