|
Size: 286
Comment: Added two easygpg concept graphics.
|
Size: 817
Comment: better phrasing of the "contract"
|
| 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? | The software components we plan to change or consider as part of the contract: * email clients (Kontact Mail and Thunderbird with Enigmail as example for others) * GnuPG backend * a service located at the email service provider * central fallback server * classic certificate ("key") server == How should an improved email client 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. |
| Line 9: | Line 19: |
| == How EasyGPG based GnuPG backend should work? | == How should an improved GnuPG backend work? |
Components
Status: Work in progress
The software components we plan to change or consider as part of the contract:
- email clients (Kontact Mail and Thunderbird with Enigmail as example for others)
- GnuPG backend
- a service located at the email service provider
- central fallback server
- classic certificate ("key") server
How should an improved email client 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.
