X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;ds=sidebyside;f=manpages%2Fnotmuch-reindex-1.mdwn;h=fca8c92aac1ffc9f9764eba8b7d123ebb95052f3;hb=219490b75a85ca18d449168575a0c7538e71612e;hp=2ca91bec82c7209dd2d1741bd423d25adae9237d;hpb=29654905e64093a5275f4a554527231072efccb9;p=notmuch-wiki diff --git a/manpages/notmuch-reindex-1.mdwn b/manpages/notmuch-reindex-1.mdwn index 2ca91be..fca8c92 100644 --- a/manpages/notmuch-reindex-1.mdwn +++ b/manpages/notmuch-reindex-1.mdwn @@ -18,8 +18,8 @@ <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. + search terms, and re-creates the full-text index on these messages usâ + ing the supplied options. Supported options for reindex include @@ -41,18 +41,47 @@ sion key is certainly 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 or - --decrypt=nostash without considering the security of your - index. + --decrypt=nostash without considering the security of your inâ + dex. See also index.decrypt in notmuch-config(1). +
+ A user just received an encrypted message without indexing its cleartâ + ext. After reading it (via notmuch show --decrypt=true), they decide + that they want to index its cleartext so that they can easily find it + later and read it without having to have access to their secret keys: + + notmuch reindex --decrypt=true id:1234567@example.com + + A user wants to change their policy going forward to start indexing + cleartext. But they also want indexed access to the cleartext of all + previously-received encrypted messages. Some messages might have alâ + ready been indexed in the clear (as in the example above). They can ask + notmuch to just reindex the not-yet-indexed messages: + + notmuch config set index.decrypt true + notmuch reindex tag:encrypted and not property:index.decryption=success + + Later, the user changes their mind, and wants to stop indexing cleartâ + ext (perhaps their threat model has changed, or their trust in their + index store has been shaken). They also want to clear all of their old + cleartext from the index. Note that they compact the database afterâ + ward as a workaround for https://trac.xapian.org/ticket/742: + + notmuch config set index.decrypt false + notmuch reindex property:index.decryption=success + notmuch compact ++
- notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1), notâ - much-hooks(5), notmuch-insert(1), notmuch-new(1), notmuch-reply(1), - notmuch-restore(1), notmuch-search(1), notmuch-search-terms(7), notâ - much-show(1), notmuch-tag(1) + notmuch(1), notmuch-compact(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), notâ + much-search-terms(7), notmuch-show(1), notmuch-tag(1)
- 2009-2018, Carl Worth and many others + 2009-2022, Carl Worth and many others-