From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: use new show --decrypt=stash feature in emacs UI
Date: Tue, 12 Jun 2018 23:07:33 -0700 [thread overview]
Message-ID: <87vaanqkwq.fsf@ligo.caltech.edu> (raw)
In-Reply-To: <87y3fj4np2.fsf@fifthhorseman.net>
[-- Attachment #1: Type: text/plain, Size: 3034 bytes --]
On Tue, Jun 12 2018, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
> On Tue 2018-06-12 10:00:18 -0400, Daniel Kahn Gillmor wrote:
>> (it'd be nice to be able to use notmuch-emacs to browse a notmuch
>> archive without locking the notmuch db or even needing read/write access
>> to the database)
>
> to be clear, it's not just about wanting to be able to avoid write
> access during "notmuch show" -- there are other use cases i'd like us to
> be able to support, including the ability to keep some messages'
> cleartext indexed, while leaving some of them un-indexed (keeping their
> contents secret from anyone who doesn't have the user's secret keys).
>
> This proposed change removes that possibility, so i think it needs more
> nuance.
This patch works for all the use cases I personally care about, so I
would like a configuration that is this simple.
The use case you're arguing for, which I believe is the ability to
choose on a per-message basis whether you want to stash or not, would
have to not use the show stash functionality at all.
What if notmuch-crypto-process-mime just accepted the same values that
show --decrypt does, with the same meanings, e.g.:
┌─────────────────────────────────────┬───────┬──────┬──────┬───────┐
│ │ false │ auto │ true │ stash │
├─────────────────────────────────────┼───────┼──────┼──────┼───────┤
│Show cleartext if session key is │ │ X │ X │ X │
│already known │ │ │ │ │
├─────────────────────────────────────┼───────┼──────┼──────┼───────┤
│Use secret keys to show cleartext │ │ │ X │ X │
├─────────────────────────────────────┼───────┼──────┼──────┼───────┤
│Stash any newly recovered session │ │ │ │ X │
│keys, reindexing message if found │ │ │ │ │
└─────────────────────────────────────┴───────┴──────┴──────┴───────┘
notmuch-crypto-process-mime is really only relevant for show anyway, so
I think this makes sense.
Users who want to chose to stash on a per-message basis would then need
to set notmuch-crypto-process-mime=true, and then do reindex
--decrypt=true if they want to stash.
jamie.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-06-13 6:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 23:09 [PATCH] emacs: use new show --decrypt=stash feature in emacs UI Jameson Graef Rollins
2018-06-12 1:33 ` Jameson Graef Rollins
2018-06-12 14:00 ` Daniel Kahn Gillmor
2018-06-12 22:58 ` Daniel Kahn Gillmor
2018-06-13 6:07 ` Jameson Graef Rollins [this message]
2018-06-13 15:23 ` Daniel Kahn Gillmor
2018-06-13 16:25 ` David Bremner
2018-06-13 17:04 ` Daniel Kahn Gillmor
2018-06-13 18:15 ` Jameson Graef Rollins
2018-06-18 0:31 ` [PATCH] emacs: new crypto customization variable to control stashing of encryption session keys Jameson Graef Rollins
2018-06-18 22:19 ` Daniel Kahn Gillmor
2018-06-18 22:49 ` Jameson Graef Rollins
2018-06-19 3:06 ` Daniel Kahn Gillmor
2018-06-19 3:26 ` Jameson Graef Rollins
2018-06-19 10:14 ` David Bremner
2018-06-19 14:46 ` Jameson Graef Rollins
2018-06-19 15:18 ` Jameson Graef Rollins
2018-06-19 15:20 ` Jameson Graef Rollins
2018-06-19 16:42 ` Daniel Kahn Gillmor
2018-06-19 20:18 ` Jameson Graef Rollins
2018-06-19 17:50 ` Jameson Graef Rollins
-- strict thread matches above, loose matches on Subject: below --
2018-06-11 23:04 [PATCH] emacs: use new show --decrypt=stash feature in emacs UI Jameson Graef Rollins
2018-06-11 23:02 Jameson Graef Rollins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vaanqkwq.fsf@ligo.caltech.edu \
--to=jrollins@finestructure.net \
--cc=dkg@fifthhorseman.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).