Daniel Kahn Gillmor a990585408 crypto: use stashed session-key properties for decryption, if available ... When doing any decryption, if the notmuch database knows of any session keys associated with the message in question, try them before defaulting to using default symmetric crypto. This changeset does the primary work in _notmuch_crypto_decrypt, which grows some new parameters to handle it. The primary advantage this patch offers is a significant speedup when rendering large encrypted threads ("notmuch show") if session keys happen to be cached. Additionally, it permits message composition without access to asymmetric secret keys ("notmuch reply"); and it permits recovering a cleartext index when reindexing after a "notmuch restore" for those messages that already have a session key stored. Note that we may try multiple decryptions here (e.g. if there are multiple session keys in the database), but we will ignore and throw away all the GMime errors except for those that come from last decryption attempt. Since we don't necessarily know at the time of the decryption that this *is* the last decryption attempt, we'll ask for the errors each time anyway. This does nothing if no session keys are stashed in the database, which is fine. Actually stashing session keys in the database will come as a subsequent patch.		2017-12-04 21:48:31 -04:00
..
notmuch-properties.rst	crypto: use stashed session-key properties for decryption, if available	2017-12-04 21:48:31 -04:00
notmuch-search-terms.rst	doc: add notmuch-properties(7)	2017-10-21 19:52:55 -03:00