summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorrnhmjoj <rnhmjoj@inventati.org>2022-08-27 23:18:00 +0200
committerrnhmjoj <rnhmjoj@inventati.org>2022-08-27 23:18:00 +0200
commit576005a34a9b3bbdb0fbe1ce1548fb1fb02fd9ef (patch)
treeb111597ded2655eb645c27b7f63b623455837a0a /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent219b71278a6dc5ea8493974b1d184096f3fd4047 (diff)
nixos/gnupg: use better trick to update the agent TTY
Long story short: the SSH agent protocol doesn't support telling from which tty the request is coming from, so the the pinentry curses prompt appears on the login tty and messes up the output and may hang. The current trick to workaround this is informing the gnupg agent every time you start a shell: this assumes you will run `ssh` in the latest tty, if you don't the latest tty will be messed up this time. The ideal solution would be updating the tty exactly when (and where) you run `ssh`. This is actually possible using a catch-all Match block in ssh_config and using the `exec` feature that hooks a command to the current shell. Source for the new trick: https://unix.stackexchange.com/a/499133/110465
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions