diff options
author | quaff <me@quaff.ca> | 2024-03-25 14:10:41 -0700 |
---|---|---|
committer | Robin Jarry <robin@jarry.cc> | 2024-04-13 21:59:44 +0200 |
commit | 163c9cbe7662e4f076b0b7089501dff1cb219761 (patch) | |
tree | a552f96572faf050a163b41ce53483a66119400e | |
parent | d94969d8f669fb2b4c463a0267865379e30ff975 (diff) | |
download | aerc-wiki.tar.gz aerc-wiki.zip |
integrations: mention gpg-agent for use over SSHwiki
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 <me@quaff.ca>
Acked-by: Robin Jarry <robin@jarry.cc>
-rw-r--r-- | integrations/pgp.md | 11 |
1 files changed, 11 insertions, 0 deletions
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 |