Comment by 🦀 jeang3nie
Re: "How to use pinentry-gtk-2 instead of pinentry-curses?"
Basically, the command "pinentry" has to be a symlink to "pinentry-gtk2". Since FreeBSD doesn't have something akin to "update-alternatives" (as you noticed) this has to be manually done.
It's best to not do this in /usr/local however, as that's managed by packages and ports and would likely get blown away on the next update anyway. I'd make a link at $HOME/bin/pinentry pointing to /usr/local/bin/pinentry-gtk2 and make sure that $HOME/bin is in your $PATH before /usr/local/bin, ensuring that your customization is seen first.
2023-08-03 · 3 years ago
2 Later Comments ↓
👾 fab [OP] · 2023-08-03 at 16:45:
@jeang3nie Thanks for your comment. I tried your solution without success. I couldn't manage to pass the right pinentry program to my script even by setting the $PATH explicitly in the script.
But I found the probably right solution: set the "pinentry-program" variable in the gpg-agent.conf to "/usr/local/bin/pinentry-gtk-2".
That solved the issue.
🦀 jeang3nie · 2023-08-03 at 19:18:
Glad it's working now for you anyway.
Original Post
How to use pinentry-gtk-2 instead of pinentry-curses? — Can somebody please tell me how to force FreeBSD to use pinentry-gtk-2 instead of pinentry-ncurses? On Debian I'd use "update-alternatives", but I'm not aware of a similar command on FreeBSD...