Feature proposal: Import S/MIME certificates from contacts when composing a message
Description
If an S/MIME encrypted e-mail is sent using recipients from the addressbook the certificates from the addressbook's contacts are ignored. Thus the user must manually export the certificate from the contact and re-import it to the certificate store.
Yet on receiving a message the sender's certificate is automatically imported to the certificate store.
Importing the certificates when composing a message would simplify the usage of S/MIME encrypted mails a lot.
Proposal
Two components need to be modified to import the certificates during composition of e-mails:
- evolution (Composer): Query certificates from the evolution-data-server when composing an e-mail and add them to the certdb
- evolution-data-server (libebook): New interface to resolve a list of certificates (if available) for an EDestination object.
Open points
-
Importing the certificates during composition is a little ugly, yet I couldn't think of a better way atm. Any proposals? -
Should there be some kind of MessageBox asking the user if the certificates shall be imported, or a global setting to enable/disable automatic import? Yet when receiving e-mails there is also no such option still the certs are imported automatically. -
Currently (see patches below) the certificates are always imported no matter if S/MIME encryption is enabled or not. Should it only be done if S/MIME encryption is enabled? -
Is a define (#define MAX_SMIME_CERTS 128) an acceptable way to limit the maximum number of certificates returned by e_destination_get_contact_certs?
Patches (Draft)
based on Evolution 3.28.5 Debian Testing, works with current master evolution: ea0ca88f, data-server: evolution-data-server@6c7dbc4d
evolution-3.28.5.patch
Edited by Ghost User