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>
---
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
--
2.44.0
quaff <me@quaff.ca> wrote:
> 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>
Applied, thanks.
To git@git.sr.ht:~rjarry/aerc
a67fd7cb544b..bd489a1c9017 master -> master