Conversation

Notices

1. Embed this notice
   lhp (lhp@mastodon.social)'s status on Tuesday, 27-Aug-2024 13:10:27 JST lhp

   in reply to

   • dnkl

   @dnkl the protocol actually has a way to set $DISPLAY without needing a command arg. In fact, there are two different ways to set various variables.

   Also there is a handy error code to indicate your implementation doesn't support some feature. But don't think about using it, because gpg-agent will just abort. Instead always say OK and silently drop it.

   gpg is the best argument against hand-rolling IPC.

   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     lhp (lhp@mastodon.social)'s status on Tuesday, 27-Aug-2024 13:10:29 JST lhp

     in reply to

     • dnkl

     @dnkl when I implemented the pinentry protocol, first I copied the messages sent by the "official" pinentry implementations bit-for-bit. It did not work. Then I tried following the protocol spec, which did end up working, kinda. However this means the official ones are doing it wrong, but somehow still work in a way I could not reproduce nor did I ever figure out why they are allowed to do it wrong while my program gets killed by gpg-agent.

   • Embed this notice
     dnkl (dnkl@emacs.ch)'s status on Tuesday, 27-Aug-2024 13:10:29 JST dnkl

     in reply to

     @lhp I'm almost more bothered by the fact that gpg-agent just assumes it can use command line arguments (like --display). I mean, why not extend the protocol if necessary? Why add an additional interface clients are just assumed to implement?

   • Embed this notice
     lhp (lhp@mastodon.social)'s status on Tuesday, 27-Aug-2024 13:10:30 JST lhp

     in reply to

     • dnkl

     @dnkl however the protocol isn't really documented. There is an assuan doc for the wire protocol and there is one for the pinentry protocol, but they disagree with each other and with reality. Also sometimes they use "character" when it really should be "byte". Not that anything actually checks line lenghts. Pinentry protocol requires lines lengths which are technically illegal with assuan, but no one seems to care there either...

   • Embed this notice
     dnkl (dnkl@emacs.ch)'s status on Tuesday, 27-Aug-2024 13:10:30 JST dnkl

     in reply to

     @lhp hey, that just makes it easier to implement; no annoying rules to follow. Right!?

   • Embed this notice
     dnkl (dnkl@emacs.ch)'s status on Tuesday, 27-Aug-2024 13:10:32 JST dnkl

     I decided to add a pinentry backend to #fuzzel.

     Turns out it's not that difficult. The protocol is line based (on STDIN). That means we can re-use a lot of code from the dmenu mode.

     Then all we need to do is force a couple of options, like --prompt-only, and we're good to go.

     We ignore most of the pinentry options and commands, since they're not applicable in fuzzel.

     Biggest downside I've found so far: since fuzzel is a layer shell application, you can't switch window focus while fuzzel is running.