unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Brian Sniffen <bts@evenmere.org>
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: Tue, 11 Jul 2017 19:01:42 -0400	[thread overview]
Message-ID: <87vamyy3vt.fsf@fifthhorseman.net> (raw)
In-Reply-To: <6987A5E2-E397-4020-A6B8-7D57BD49B225@evenmere.org>

On Mon 2017-07-10 20:48:40 -0400, Brian Sniffen wrote:
> 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.

Could you point to the zip bomb problem, Brian?  the quine (infinite
zipbomb) i think is limited by some sort of hard-coded depth constant.
are you referring to an infinite blowup, or "just" a finite expansion?

i agree that i expect GMime to be subject to finite expansions as well
(i haven't experimented with them though), but i think neither gpg nor
GMime should be subject to infinite expansion.

if you think otherwise, i'd be happy to read pointers.

thanks for raising this concern!

       --dkg

  reply	other threads:[~2017-07-11 23:03 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
2017-07-11 23:01     ` Daniel Kahn Gillmor [this message]
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=87vamyy3vt.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=bts@evenmere.org \
    --cc=david@tethera.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).