[sup-talk] sup leaves unencrypted emails in /tmp

From: Hamish D <dmishd@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] sup leaves unencrypted emails in /tmp
Date: Thu, 2 Dec 2010 00:18:08 +0000	[thread overview]
Message-ID: <AANLkTikzfKZ9573c+NOiYA3UWjFhWpohhcGroS0Zz19F@mail.gmail.com> (raw)

I noticed that sup appears to leave the unencrypted contents of emails
in /tmp - at least it did on my system. This is a pretty serious issue
on shared computers. I'm not sure why - my attempts at a quick fix
failed. The files are created using Tempfile.new and close is called,
but after that the files are written to by gpg. I'm not sure if this
means that the tempfile system then doesn't delete them later for some
reason.

The tempfile stuff does seem to work for the files containing the
output from gpg. They do (eventually) get deleted. But the "temporary"
files that gpg puts the plaintext into seem to hang around even after
I've done a clean exit from sup.

If anyone has got good ideas about how to fix this for sup 0.12 I
think that would be a fine thing to do.

Note that this is the mainline version of sup, not the gpgme version
I've been developing - using gpgme means the plaintexts never have to
be written to disk, so if we move to gpgme (once I've got it up to
scratch) then these problems will go away.

Thought people ought to know.
Hamish Downer
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk