unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Varac <varac@leap.se>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org
Subject: Re: Header protection / memoryhole [was: Re: Header encryption / memoryhole]
Date: Mon, 09 Apr 2018 12:23:44 +0200	[thread overview]
Message-ID: <152326942407.5117.4428846108935868174@rocinante.bitrigger.de> (raw)
In-Reply-To: <87o9itwg5x.fsf@fifthhorseman.net>

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

Hi Daniel,

Thanks for clarifying!

Greetings, Varac


Quoting Daniel Kahn Gillmor (2018-04-08 23:18:34)
> On Mon 2018-04-02 18:58:28 +0200, Varac wrote:
> 
> > I'd like to know the state of header encryption support for
> > notmuch (aka memoryhole) [1].
> 
> "memoryhole" refers to "protected headers", not just encrypted headers.
> That is, the headers can be protected both by cryptographic signature
> *and* by encryption.  This is a subtlety, but probably worth getting
> right as we work on documentation and implementations.
> 
> This is on my list of things to work on for notmuch, but i'd be happy if
> someone else beat me to it.  clearly i've taken too long to get this
> done.
> 
> fwiw, memory-hole messages do display successfully in all versions of
> notmuch i'm aware of, but they do so by rendering the "force-display"
> part.  so notmuch currently uses the fallback arrangements as explicitly
> intended by the original memoryhole draft.
> 
> as i see it, the steps are (in order):
> 
>  * handle encrypted subject correctly during message display time if the
>    message is being decrypted.
>  
>  * handle encrypted subject specifically during message decryption at
>    indexing time, storing it the correct subject field, instead of
>    storing the "outside" subject.
> 
>  * suppress display of any "force-display" part during message display
>    time.
> 
>  * handle any other cryptographically-protected headers during display
>    and indexing.
> 
>  * generate protected headers when encrypting mail.
> 
> 
> i welcome help with any of these steps :)
> 
>   --dkg

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

-----BEGIN PGP SIGNATURE-----

iQIcBAABCgAGBQJayz8vAAoJEFRl5354du0EfXIP/1RMV0QteRrAuM9amCwSzoiq
oCGKu0nU3ZpXE8D1/5rvIa4n1e/26xXh8uOJlSx8Bq9J3mZ+2tq5Ev+vPm8wVc6M
xs64pC/IF1Ver4IBYdogDZuV/QIkZllrxQYjqeERYRb44W1Idzj38YSCayp9bijG
Kg6r4WzxS3vz+syqz8PjADqfkMqu+e5X2UBvg+//A9u1Bq8qHHvE5KlkDrKngqbj
oXI3YVgeRt91IEO6o12HxvdBWK7lEc3rWXtrndQiBQaNGzCW4M5Tkriy/W3Z3crF
IK+wCK3rTRJ/yQemv3s7JsumKuVHRlX5qMlnARFO7u+jt5Gk86t3Zxr8ysFoQpOX
UQkcSDeZ5SClKbSoXjy+JCquc5nqsnJwDA0rg3v70at289qfVs3+wT//uk/ZB3Cb
wsKkqrgo3bJ5hhpdAM9hbeUF/X1/7m/lfTfSb1Ghbr5b8YBFhE7RQLJF8pOjA2kY
Izf7He5oCMBt0zSUxny0g7fh0P+I6WgLXi5TCDZEnfNsdXJpCW3IhczK1dIw40/6
r0W4CkHjduQM95QChox+LVqN1dEzgSIxtNoMSOSqTd/bEQzblnYXIJNgAMCq/vSB
4FxunqCiWl9V7OaWR4VE9NdrzOLQi1+vohwALTQ3FTQXPyUHaSCSVvLw/BXySAI+
Mq7WewrPTS0KP2+zmw0o
=8eXr
-----END PGP SIGNATURE-----

      reply	other threads:[~2018-04-09 10:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02 16:58 Header encryption / memoryhole Varac
2018-04-08 21:18 ` Header protection / memoryhole [was: Re: Header encryption / memoryhole] Daniel Kahn Gillmor
2018-04-09 10:23   ` Varac [this message]

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=152326942407.5117.4428846108935868174@rocinante.bitrigger.de \
    --to=varac@leap.se \
    --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).