| | |
| | | + PGP: key generation (client- or server-side) |
| | | + Handling of PGP keys attached to incoming messages |
| | | + User preferences to disable plugin features |
| | | + Attaching public keys to email |
| | | |
| | | |
| | | TODO: |
| | | ------------- |
| | | ----- |
| | | - Handling of big messages with temp files |
| | | - Key info in contact details page (optional) |
| | | - Extended key management: |
| | |
| | | - Generate revocation certs |
| | | - Search filter to see invalid/expired keys |
| | | - Key server(s) support (search, import, upload, refresh) |
| | | - Attaching public keys to email |
| | | - Mark keys as trusted/untrasted, display appropriate message in verify/decrypt status |
| | | - Change attachment icon on messages list for encrypted messages (like vcard_attachment plugin does) |
| | | - Support for multi-server installations (store keys in sql database?) |
| | |
| | | - S/MIME: Sending signed/encrypted messages |
| | | - S/MIME: Handling of certs attached to incoming messages |
| | | - S/MIME: Certificate info in Contacts details page (optional) |
| | | |
| | | |
| | | KNOWN ISSUES: |
| | | ------------- |
| | | There are some know issues with accepting key passphrases on various |
| | | system configurations. This is caused by issues in PinEntry handling. |
| | | Make sure that vendor/bin/crypt-gpg-pinentry works from command line. |
| | | Possible reasons: |
| | | - non-supported GnuPG version, i.e. >= 2.1 |
| | | - non-working loader in shebang (#! /usr/bin/env php) |