mirror/FairEmail
1
0
Fork 0
mirror of https://github.com/M66B/FairEmail.git synced 2024-12-27 02:07:12 +00:00
Code Issues Releases Wiki Activity

Updated FAQ

Browse source
This commit is contained in:
M66B 2021-03-02 11:44:00 +01:00
parent f9295d680b
commit c456af284d
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
FAQ.md
View file

@ -666,6 +666,8 @@ Communication with email servers is always encrypted, unless you explicitly turn
This question is about optional end-to-end encryption with PGP or S/MIME.
The sender and recipient should first agree on this and exchange signed messages to transfer their public key to be able to send encrypted messages.
<br />
*General*
Please [see here](https://en.wikipedia.org/wiki/Public-key_cryptography) about how public/private key encryption works.
@ -698,6 +700,8 @@ but be aware that automatic decryption is not possible if user interaction is re
The to be encrypted message text/attachments and the decrypted message text/attachments are stored locally only and will never be added to the remote server.
If you want to undo decryption, you can use the *resync* menu item in the three-dots menu of the message action bar.
<br />
*PGP*
You'll need to install and configure [OpenKeychain](https://f-droid.org/en/packages/org.sufficientlysecure.keychain/) first.
@ -745,6 +749,8 @@ Common errors:
* *Missing key for encryption*: there is probably a key selected in FairEmail that does not exist in the OpenKeychain app anymore. Resetting the key (see above) will probably fix this problem.
* *Key for signature verification is missing*: the public key for the sender is not available in the OpenKeychain app. This can also be caused by Autocrypt being disabled in the encryption settings or by the Autocrypt header not being sent.
<br />
*S/MIME*
Encrypting a message requires the public key(s) of the recipient(s). Signing a message requires your private key.
@ -809,6 +815,16 @@ openssl pkcs12 -in filename.pfx/p12 -clcerts -nokeys -out cert.pem
You can decode S/MIME signatures, etc, [here](https://lapo.it/asn1js/).
<br />
*pretty Easy privacy*
pretty Easy privacy (p≡p) is not supported
because there is still [no approved standard](https://tools.ietf.org/id/draft-birk-pep-00.html) for this
and because hardly anyone uses this.
<br />
S/MIME sign/encrypt is a pro feature, but all other PGP and S/MIME operations are free to use.
<br />