On Wed, Dec 07, 2016 at 01:55:16PM +0000, isdtor wrote:
> Could mutt, upon invoking view-mailcap, save all attachments to a temp
> directory and rewrite the html part so that the img src paths are
> correct?

TBH, for maximum security it should really do this anyway, for ALL
temporary files.  Creating a temporary directory, setting its
permissions to 0700 and putting all of your temporary files in that
directory is the safest way to avoid symlink attacks and the rest of
the class of temp file vulnerabilities that typically pop up.  [NOTE:
I'm not talking about saving attachments--just temp files.]  It would
also make it easier to clean up old temporary files that Mutt failed
to clean up due to crashed sessions or other bugs (because they'd all
be in their own mutt-specific temp directory, so you could just cd
into it and rm * once you were sure there were no mutt sessions
running).  I believe I've suggested that before on this list...  and I
even have a little module that could be used for it, which I'd be
happy to provide.  I might even be able to find the time to convert
mutt's various temp file management code...

In any event, I think both parts of what you're suggesting would be
good improvements:

1. Put temporary content in its own directory inside $TMPDIR or
   equivalent (avoids symlink attacks and such completely)
2. Extract all of the mime parts of HTML mail into said directory so a
   browser can display them.

These do seem like separate issues to me, and I tend to think probably
it's worth creating two bugs for them.

-- 
Derek D. Martin    http://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail due to spam prevention.  Sorry for the inconvenience.

Attachment: pgpzF4b7CN77i.pgp
Description: PGP signature

Reply via email to