Updated FAQ

This commit is contained in:
Marcel Bokhorst 2021-03-02 21:44:23 +01:00 committed by GitHub
parent 170e5442a6
commit 7df615f35c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions

4
FAQ.md
View File

@ -819,9 +819,9 @@ You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
*pretty Easy privacy*
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and not many people use it.
There is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for pretty Easy privacy (p≡p) and not many people are using it.
However, FairEmail can send and receive PGP encrypted messages, which is compatible with p≡p.
However, FairEmail can send and receive PGP encrypted messages, which are compatible with p≡p.
Also, FairEmail understands incoming p≡p messages since version 1.1519,
so the encrypted subject will be shown and the embedded message text will be shown more nicely.