On Thu, 3 Nov 2016 16:13, d...@fifthhorseman.net said: > i do not either, but i will work on a patch that provides something > approximating this approach today.
Thanks. > I'm not sure why you prefer it that way. If pinentry is used as a Because the pinentry code makes assumptions on how it has been initialized. Changing this by switching the UI method on the fly needs a closer analysis of the side effects. Pinentry is also not designed as a long running process - it is easier to terminate pinentry and let the caller start a different pinentry. It would for example be possible to tell the caller (gpg-agent), that it should try a different pinentry version the next time it calls pinentry. This way we could get around the gnome problems. But sure it would also be surprising if sometimes the GTK or QT pinentry pops up instead of the GNOME pinentry . Even more surprising than the fallback to Curses. BTW, the fallback to Curses can also be troublesome if the calling application does not know about this and has no way to redraw the screen. > It would be great to get better error messages in the hands of users. > Anything in that direction is welcome. I'll look into this. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
pgpW94nceR4Hs.pgp
Description: PGP signature
