HomePhorge

Another attempt at circumventing the dreaded pinentry-curses

Description

Another attempt at circumventing the dreaded pinentry-curses

The compile option is just to avoid confusion really.
It doesn't seem to be the fallbacks fault (which primarily checks the
DISPLAY env var).
One reproducible scenario is that we start kube without the
wrappper-script, which ends up starting gpg-agent without the
necessary options, thus finding pinentry-curses in /usr/bin (instead
of what we install ourselves.
We thus now always kill a running gpg-agent first, so we can indeed launch a
new one that has the option set. This fixes at leaset the scenario
above.

Details

Provenance
Christian Mollekopf <chrigi_1@fastmail.fm>Authored on Sep 13 2018, 5:19 PM
mollekopfPushed on Sep 13 2018, 5:21 PM
Parents
rFKUBE28a6f631818b: Also enable extensions for the experimental flatpak
Branches
Unknown
Tags
Unknown
Build Status
Buildable 20342

Event Timeline

Christian Mollekopf <chrigi_1@fastmail.fm> committed rFKUBE4ce9330826cc: Another attempt at circumventing the dreaded pinentry-curses (authored by Christian Mollekopf <chrigi_1@fastmail.fm>).Sep 13 2018, 5:19 PM