Pinentry-mode loopback doesn't tell the user which PIN it's asking for
Jernej Jakob via Gnupg-devel <[email protected]> Tue, 5 May 2026 11:51:44 +0200
| Newsgroups | gmane.comp.encryption.gpg.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============8854010361032576164== Content-Type: multipart/signed; boundary="Sig_/ZvEYIwN6vLRRtFJm_BYgCov"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Sig_/ZvEYIwN6vLRRtFJm_BYgCov Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I have a GUI-less system that I use gpg on, I use it in GNU screen, I tried to set it to use pinentry-tty but that conflicts with screen and it breaks input (IIRC it doubles all characters or is otherwise unusable, it's been a while since I tested it). It works fine with pinentry-mode=3Dloopback, but it doesn't say which PIN it's asking for, so I have to work from memory, knowing which PIN it's asking for which particular command. Is it possible to make gpg say which PIN it's asking for, the same way that pinentry does? --Sig_/ZvEYIwN6vLRRtFJm_BYgCov Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iJEEARYKADkWIQT+SjyZ3Ml0poPUBgMek2SE/+i6aQUCafm9sBsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMiwyLDIACgkQHpNkhP/oummrwAD9ETOD2n7qgp9SDN9m6KQD IzP8rDXQyWI/rknMNOY/5eUBAPh7cQ2PodiD0wJeYAvTTaXaR1KCASe4T7YsG+9R FEgD =8AoJ -----END PGP SIGNATURE----- --Sig_/ZvEYIwN6vLRRtFJm_BYgCov-- --===============8854010361032576164== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gnupg-devel mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-devel --===============8854010361032576164==--