[ISSUE] GPG isn't well configured

[ISSUE] GPG isn't well configured

[rivanfebrian123]

[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]

New issue by rivanfebrian123 on void-packages repository

https://github.com/void-linux/void-packages/issues/32456

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  * Void 5.13.9_1 x86_64-musl GenuineIntel uptodate rrFFF

* package:  
  * gnupg2-2.2.29_1

### Expected behavior
It should be already configured by default

### Actual behavior
```
[rivanfebrian123@RVN Clusterify]$ git commit -S -m "first commit"
error: gpg failed to sign the data
fatal: failed to write commit object

[rivanfebrian123@RVN Clusterify]$ echo "test" | gpg2 --clearsign
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

test
gpg: signing failed: Not a tty
gpg: [stdin]: clear-sign failed: Not a tty
```

Rahul Thakur's answer (https://stackoverflow.com/a/61314861) should fix this problem

### Steps to reproduce the behavior
Do a first commit

Re: GPG isn't well configured

[sgn]

[-- Attachment #1: Type: text/plain, Size: 298 bytes --]

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/issues/32456#issuecomment-896804511

Comment:
You may need to try a GUI `pinentry` likes `pinentry-gtk` `pinentry-gnome` `pinentry-qt` or `pinentry-dmenu` instead.

As of it's, working as intended, IMHO.

Re: GPG isn't well configured

[rivanfebrian123]

[-- Attachment #1: Type: text/plain, Size: 360 bytes --]

New comment by rivanfebrian123 on void-packages repository

https://github.com/void-linux/void-packages/issues/32456#issuecomment-896841453

Comment:
Thanks for your tips! I don't know much about `pinentry` stuffs, but it does work (check: https://stackoverflow.com/a/61314861).  I think the `gnupg2` package should require and configure `pinentry` by default

Re: [ISSUE] [CLOSED] GPG isn't well configured

[sgn]

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

Closed issue by rivanfebrian123 on void-packages repository

https://github.com/void-linux/void-packages/issues/32456

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  * Void 5.13.9_1 x86_64-musl GenuineIntel uptodate rrFFF

* package:  
  * gnupg2-2.2.29_1

### Expected behavior
It should be already configured by default

### Actual behavior
```
[rivanfebrian123@RVN Clusterify]$ git commit -S -m "first commit"
error: gpg failed to sign the data
fatal: failed to write commit object

[rivanfebrian123@RVN Clusterify]$ echo "test" | gpg2 --clearsign
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

test
gpg: signing failed: Not a tty
gpg: [stdin]: clear-sign failed: Not a tty
```

Rahul Thakur's answer (https://stackoverflow.com/a/61314861) should fix this problem

### Steps to reproduce the behavior
Do a first commit

Re: GPG isn't well configured

[sgn]

[-- Attachment #1: Type: text/plain, Size: 699 bytes --]

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/issues/32456#issuecomment-896859247

Comment:
Yes, I know about loopback, if you start a GUI session, you should use GUI pinentry or other GUI keyrings.

`pinentry-curses` will start in the same terminal you gui session was started, I also use pinentry-curses, but I know it cavet.

> Thanks for your tips! I don't know much about `pinentry` stuffs, but it does work (check: https://stackoverflow.com/a/61314861). I think the `gnupg2` package should require and configure `pinentry` by default

You can take it to gnupg's developer https://lists.gnupg.org/pipermail/gnupg-devel/2016-April/031012.html

Re: GPG isn't well configured

[sgn]

[-- Attachment #1: Type: text/plain, Size: 257 bytes --]

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/issues/32456#issuecomment-896860264

Comment:
And loopback is considered security risk upstream https://lists.gnupg.org/pipermail/gnupg-devel/2016-April/031016.html

Re: GPG isn't well configured

[sgn]

[-- Attachment #1: Type: text/plain, Size: 278 bytes --]

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/issues/32456#issuecomment-896860264

Comment:
And loopback is considered security risk (if used carelessly) upstream https://lists.gnupg.org/pipermail/gnupg-devel/2016-April/031016.html