|
Size: 164
Comment:
|
Size: 727
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| Line 5: | Line 4: |
| == How EasyGPG based email client should work? TODO |
The ~EasyGpg components: * email client (e.g. Kontact Mail, Thunderbird with Enigmail) * GnuPG backend * email service provider * central fallback server * classic certificate ("key") server |
| Line 9: | Line 12: |
| == How EasyGPG based GnuPG backend should work? TODO |
== How an EasyGpg based email client should work? User A wants to send a signed/encrypted email to user B. A has only the email address of B. A's email client gets the OpenPGP (public) certificate from B's email service provider (step 1+2) which is used to encrypt the email to B. {{easygpg-send-email.png}} [[attachment:easygpg-send-email.pdf|PDF]] == How an EasyGpg based GnuPG backend should work? {{easygpg-backend.png}} [[attachment:easygpg-backend.pdf|PDF]] |
Components
Status: Work in progress
The EasyGpg components:
- email client (e.g. Kontact Mail, Thunderbird with Enigmail)
- GnuPG backend
- email service provider
- central fallback server
- classic certificate ("key") server
How an EasyGpg based email client should work?
User A wants to send a signed/encrypted email to user B. A has only the email address of B. A's email client gets the OpenPGP (public) certificate from B's email service provider (step 1+2) which is used to encrypt the email to B.
