Re: Pinentry-mode loopback doesn't tell the user which PIN it's asking for
Werner Koch via Gnupg-devel <[email protected]> Tue, 05 May 2026 13:45:17 +0200
| Newsgroups | gmane.comp.encryption.gpg.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============5918133566451325799== Content-Type: multipart/signed; boundary="=William_Gates_IED_Indigo_national_information_infrastructure_FAA=Com"; micalg=pgp-sha512; protocol="application/pgp-signature" --=William_Gates_IED_Indigo_national_information_infrastructure_FAA=Com Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 5 May 2026 11:51, Jernej Jakob said: > It works fine with pinentry-mode=3Dloopback, but it doesn't say which PIN That is a kludge for unattended use. > Is it possible to make gpg say which PIN it's asking for, the same way > that pinentry does? No, it does not know. gpg-agent knows that. Either you write your own pinentry in a simialr manner as Emacs did it. Or if you have no GUI, just use a curses based Pinentry or the pinentry-tty. The curses mode is actually the fallback for the GUI pinentries if DISPLAY is not set. You may need to redraw the screen, as it is the case with many curses applications, but gpg supports this by emitting a PINENTRY_LAUNCHED status line. Salam-Shalom, Werner =2D-=20 The pioneers of a warless world are the youth that refuse military service. - A. Einstein --=William_Gates_IED_Indigo_national_information_infrastructure_FAA=Com Content-Type: application/pgp-signature; name="openpgp-digital-signature.asc" -----BEGIN PGP SIGNATURE----- iJ8EARYKAEcWIQSHd0YfKgdOvEgNNZQZzByeCFsQegUCafnYTRsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMSwyLDINHHdrQGdudXBnLm9yZwAKCRAZzByeCFsQejX+APwL bVNSra2hbtTpfL3OIY3+ltmwwYIWD5tSSuUTU05z2gEAgMmDdiJyJGwab7sUSf0A dcrys6F6Bewh1xU+c7smogk= =qnuO -----END PGP SIGNATURE----- --=William_Gates_IED_Indigo_national_information_infrastructure_FAA=Com-- --===============5918133566451325799== 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 --===============5918133566451325799==--