On Mon, 2020-10-12 at 13:08 +0200, Jörg Jellissen wrote: Hello, i have a problem with my access rules on my ~/.gnupg folder. The reason is that i can't sign any e-mails . the warning message was that the access rules to the folder are too open but which rights are correct? i have looked in the folder and my rights looks like this drwxr-xr-x 3 joerg users 4,0K 12. Okt 12:57 . drwx------ 29 joerg users 4,0K 11. Okt 18:48 .. drwx------ 2 joerg users 4,0K 9. Okt 21:13 private-keys-v1.d -rw-r--r-- 1 joerg users 2,5K 9. Okt 21:13 pubring.kbx -rw------- 1 joerg users 32 9. Okt 21:13 pubring.kbx~ -rw-r--r-- 1 joerg users 7 10. Okt 19:41 reader_0.status -rw------- 1 joerg users 1,3K 9. Okt 21:13 trustdb.gpg is this correct for gpg / Kleopatra? the translated output was Detailed error message: Output from gpg2: gpg: WARNING: Insecure access rights of the home directory `/home/joerg/.gnupg ' gpg: write after '-' gpg: pinentry launched (5745 curses 1.1.0 - -: 0) gpg: Authentication failed: Inappropriate IOCTL (I / O control) for the device gpg: signing failed: Unsuitable IOCTL (I / O control) for the device Many thanks for helpers Seems like there is an issue with the pinentry binary. It does not seem to be compatible with your system. IOCTL are a way to interface with the kernel, they export extra "functions" in file descriptors that you can call. Your system does not support whatever the pinentry is trying to use. You can use strace to try to figure you exactly what is wrong with your pinentry. I'd recommend to open an issue in the upstream to see if they could implement things in an alternative that does not require use of the problematic IOCTL. Cheers, Filipe Laíns
Attachment:
signature.asc
Description: This is a digitally signed message part
