summaryrefslogtreecommitdiff
path: root/integrations/pgp.md
blob: 2e826ef0017989a9fa635fc9d6412843dca972bd (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
---
title: "aerc-wiki: Integrations/PGP"
---

# PGP

To use GnuPG, simply set the following in `aerc.conf`.  Unless if you want to
tinker with the internal implementation, **it is highly recommended that you
use gpg or similar external implementations.**
```conf
[general]
pgp-provider=gpg
```

When the above configuration option is unset or set to `internal`,
aerc uses an internal OpenPGP implementation.

> At the moment internal PGP support is still in it's early stages and will
> likely change as time goes on. Tickets relating to this can be found in
> ~sircmpwn's tracker: [#353](https://todo.sr.ht/~sircmpwn/aerc2/353)
> [#354](https://todo.sr.ht/~sircmpwn/aerc2/354)
> [#355](https://todo.sr.ht/~sircmpwn/aerc2/355)
> [#357](https://todo.sr.ht/~sircmpwn/aerc2/357)
> [and more](https://todo.sr.ht/~sircmpwn/aerc2?search=label%3A%22pgp%22)

**Please be aware:** at the moment internal PGP support requires you to export
your private keys. Please ensure that your home directory is protected against
unauthorised access.

To create a PGP-Keyring and fill it with your keys from GPG, you can run the
following commands:

```shell
gpg --export >> ~/.local/share/aerc/keyring.asc
gpg --export-secret-keys >> ~/.local/share/aerc/keyring.asc
```