unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: new crypto customization variable to control stashing of encryption session keys
Date: Tue, 19 Jun 2018 13:18:00 -0700	[thread overview]
Message-ID: <87vaaejzt3.fsf@ligo.caltech.edu> (raw)
In-Reply-To: <87y3fa20f7.fsf@fifthhorseman.net>

[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]

On Tue, Jun 19 2018, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
> This is looking good to me, thanks!
>
> two more bits of nit-pickery below:
>
> On Tue 2018-06-19 08:20:12 -0700, Jameson Graef Rollins wrote:
>> +(defcustom notmuch-show-stash-session-keys nil
>> +  "Should session keys be stashed when decrypting messages for display?
>> +
>> +If this variable is non-nil session keys recovered while
>> +decrypting messages for display will be stored in the database.
>> +See description of --decrypt option in notmuch-show(1) for more
>> +information.
>
> do we want to include a warning here about the security of the index?
> setting this value to true not only stashes the session keys, but it
> also indexes the cleartext.  at the moment we're not directing people to
> the same kind of warnings ("Be aware that the index… DO NOT USE …
> without considering the security of your index.") that are present
> already in notmuch-reindex(1) and notmuch-new(1) and notmuch-insert(1).
> Perhaps notmuch-show(1) needs the same boilerplate warning, and we could
> replicate some short version of it here too?

I was wondering if it would make sense to have a separate man page for
describing all the intricacies of notmuch's crypto functionality,
i.e. notmuch-crypto(7).  There's going to be a lot of
redundancy/boilerplate in all the different man pages, and it seems like
it would be useful to put it all in one place and just reference it from
all the others.

This could also be a good place to describe how protected headers are
handled, and autocrypt once we finally get around to implementing it.

>> +NOTE: Stashing encryption session keys requires opening the
>> +notmuch database in read/write mode, which is not normally done
>
> i'd say "not otherwise done" instead of "not normally done", since we
> don't want to claim that people who use this feature aren't "normal" :)

But the claim wouldn't not be true!

I'll push another (five copies of a new) version.

jamie.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-06-19 20:18 UTC|newest]

Thread overview: 21+ 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
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 [this message]
2018-06-19 17:50       ` 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=87vaaejzt3.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).