mirror of
https://git.notmuchmail.org/git/notmuch
synced 2024-11-22 10:58:10 +01:00
29648a137c
If you're going to store the cleartext index of an encrypted message, in most situations you might just as well store the session key. Doing this storage has efficiency and recoverability advantages. Combined with a schedule of regular OpenPGP subkey rotation and destruction, this can also offer security benefits, like "deletable e-mail", which is the store-and-forward analog to "forward secrecy". But wait, i hear you saying, i have a special need to store cleartext indexes but it's really bad for me to store session keys! Maybe (let's imagine) i get lots of e-mails with incriminating photos attached, and i want to be able to search for them by the text in the e-mail, but i don't want someone with access to the index to be actually able to see the photos themselves. Fret not, the next patch in this series will support your wacky uncommon use case.
59 lines
1.7 KiB
ReStructuredText
59 lines
1.7 KiB
ReStructuredText
===============
|
|
notmuch-reindex
|
|
===============
|
|
|
|
SYNOPSIS
|
|
========
|
|
|
|
**notmuch** **reindex** [*option* ...] <*search-term*> ...
|
|
|
|
DESCRIPTION
|
|
===========
|
|
|
|
Re-index all messages matching the search terms.
|
|
|
|
See **notmuch-search-terms(7)** for details of the supported syntax for
|
|
<*search-term*\ >.
|
|
|
|
The **reindex** command searches for all messages matching the
|
|
supplied search terms, and re-creates the full-text index on these
|
|
messages using the supplied options.
|
|
|
|
Supported options for **reindex** include
|
|
|
|
``--decrypt=(true|auto|false)``
|
|
|
|
If ``true``, when encountering an encrypted message, try to
|
|
decrypt it while reindexing, storing any session keys
|
|
discovered. If ``auto``, and notmuch already knows about a
|
|
session key for the message, it will try decrypting using that
|
|
session key but will not try to access the user's secret keys.
|
|
If decryption is successful, index the cleartext itself.
|
|
|
|
If ``false``, notmuch reindex will also delete any stashed
|
|
session keys for all messages matching the search terms.
|
|
|
|
Be aware that the index is likely sufficient to reconstruct
|
|
the cleartext of the message itself, so please ensure that the
|
|
notmuch message index is adequately protected. DO NOT USE
|
|
``--decrypt=true`` without considering the security of your
|
|
index.
|
|
|
|
See also ``index.decrypt`` in **notmuch-config(1)**.
|
|
|
|
SEE ALSO
|
|
========
|
|
|
|
**notmuch(1)**,
|
|
**notmuch-config(1)**,
|
|
**notmuch-count(1)**,
|
|
**notmuch-dump(1)**,
|
|
**notmuch-hooks(5)**,
|
|
**notmuch-insert(1)**,
|
|
**notmuch-new(1)**,
|
|
**notmuch-reply(1)**,
|
|
**notmuch-restore(1)**,
|
|
**notmuch-search(1)**,
|
|
**notmuch-search-terms(7)**,
|
|
**notmuch-show(1)**,
|
|
**notmuch-tag(1)**
|