From 163c9cbe7662e4f076b0b7089501dff1cb219761 Mon Sep 17 00:00:00 2001 From: quaff Date: Mon, 25 Mar 2024 14:10:41 -0700 Subject: integrations: mention gpg-agent for use over SSH Add mention for usage over SSH. Using GPG integration with pinentry over ssh prevents entry of passphrases. Current version of aerc retains control of TTY over pinetry. Forwarding the gpg-agent will enable a workflow for users of aerc over SSH. Signed-off-by: quaff Acked-by: Robin Jarry --- integrations/pgp.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/integrations/pgp.md b/integrations/pgp.md index 2e826ef0..469c3ca3 100644 --- a/integrations/pgp.md +++ b/integrations/pgp.md @@ -34,3 +34,14 @@ following commands: gpg --export >> ~/.local/share/aerc/keyring.asc gpg --export-secret-keys >> ~/.local/share/aerc/keyring.asc ``` + +## Using `aerc` with GnuPG over SSH + +If you've tried to integrate GnuPG with aerc over SSH, you might have +encountered an issue where pinentry fails to function properly. This occurs +because pinentry lacks control over the tty while aerc maintains control. + +For guidance on resolving this, you may find assistance in the following +Arch Linux wiki page: [Forwarding gpg-agent and ssh-agent to remote][arch]. + +[arch]: https://wiki.archlinux.org/title/GnuPG#Forwarding_gpg-agent_and_ssh-agent_to_remote -- cgit v1.2.3-54-g00ecf