unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Brian Sniffen <bts@evenmere.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: David Bremner <david@tethera.net>,
	notmuch@freelists.org, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: change default for notmuch-crypto-process-mime to t
Date: Mon, 10 Jul 2017 20:48:40 -0400	[thread overview]
Message-ID: <6987A5E2-E397-4020-A6B8-7D57BD49B225@evenmere.org> (raw)
In-Reply-To: <8760f010si.fsf@fifthhorseman.net>

Gpg is exposed to some zip bomb problems last I looked. But the worst that could do is fill your disk or crash your Emacs, right?  And I suspect the MIME library exposes similar issues in quantity. 

-- 
Brian Sniffen

> On Jul 10, 2017, at 4:42 PM, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
> 
>> On Sun 2017-07-09 07:46:14 -0300, David Bremner wrote:
>> There are some cases like remote usage where this might cause
>> problems, but those users can easily customize the variable. The
>> inconvenience seems to be outweighed by the security benefit for most
>> users.
> 
> lgtm.  i'm not sure that this change is technically a "security
> benefit", though, it looks more like a "usability benefit", since the
> main use of process-crypto is likely to be decrypting messages.
> 
> for signature verification, there's some small security benefit, but
> since it's mainly exposure of interesting information to the user (as
> opposed to blocking users from doing unsafe things) it's still probably
> more on the usability side than security.
> 
> still, i think it's a good change.  If it uncovers performance problems
> on use cases that normal people care about, hopefully we can get
> examples of those use cases and get the performance problems fixed
> (rather than just encouraging those users to set the flag to nil).
> 
>     --dkg
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> https://notmuchmail.org/mailman/listinfo/notmuch

  reply	other threads:[~2017-07-11  0:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-09 10:46 [PATCH] emacs: change default for notmuch-crypto-process-mime to t David Bremner
2017-07-10 10:24 ` Tomi Ollila
2017-07-10 20:42 ` Daniel Kahn Gillmor
2017-07-11  0:48   ` Brian Sniffen [this message]
2017-07-11 23:01     ` Daniel Kahn Gillmor
2017-07-12 10:48 ` David Bremner
2017-07-15 12:14   ` David Bremner

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=6987A5E2-E397-4020-A6B8-7D57BD49B225@evenmere.org \
    --to=bts@evenmere.org \
    --cc=david@tethera.net \
    --cc=dkg@fifthhorseman.net \
    --cc=notmuch@freelists.org \
    --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).