Created attachment 897836 [details] pinentry-wrapper Hello, When trying to think about how to properly solve bug 853961 I realized that, currently administrators need to choose one pinentry implementation for all the users. That leads to some issues like, for example, if the machine is used by KDE and Gnome users, one of them will use the "non-preferred" version. Also, looking to x11-wm/enlightenment, www-plugins/passff-host, I think that their users would also benefit from a more "automated" and runtime detection method to launch the proper pinentry backend. I have seen that Fedora and OpenSuSE are using the attached wrapper. One option could be to provide it as another eselect option. That option could be the default one to try auto-detection by default, while still allowing people to force a different want if they really wish to. Thanks a lot for considering it
Sounds good to me. Would you ship the wrapper along with the eselect package?
I was thinking on providing it with app-crypt/pinentry because all the other implementations are installed by it. But I have no preference and eselect-pinentry can also be a good candidate
This seems reasonable to do. Here's the updated version of the script: https://src.fedoraproject.org/rpms/pinentry/blob/rawhide/f/pinentry-wrapper For some reason, though, it prefers pinentry-tty to pinentry-curses. We might want to swap that (since a USE flag enables it)
I see a bunch of $DISPLAY checks and a call to xprop. That script probably needs to be updated for Wayland.
It seems that, in the absence of xprop, it will rely on KDE_FULL_SESSION to detect a kde session
(In reply to Pacho Ramos from comment #5) > It seems that, in the absence of xprop, it will rely on KDE_FULL_SESSION to > detect a kde session Ah I see; it has a --display command line option and the DISPLAY logic is meant to support that. Looks fine I guess.
