From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: bug: epg send unencrypted data in trash
Date: Fri, 11 Feb 2011 13:54:07 -0600 [thread overview]
Message-ID: <87sjvuxs80.fsf@lifelogs.com> (raw)
In-Reply-To: 87k4h6sahe.fsf@gmail.com
On Fri, 11 Feb 2011 19:16:13 +0100 Thierry Volpiatto <thierry.volpiatto@gmail.com> wrote:
TV> Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:
>> i start using recently delete-by-moving-to-trash.(i had no trash before)
>> So now when i decrypt a file and read it in emacs, i have an unencrypted
>> file world readable 'epg-output-xxx' in the trash.
>> That's bad.
TV> So if one use gnus with a .authinfo.gpg, and use also
TV> delete-by-moving-to-trash, he will have the bad surprise to find his
TV> authinfo data in clear text in the trash.
TV> Maybe let-bind delete-by-moving-to-trash in epg-delete-output-file would
TV> be good.
TV> It's what i will do here anyway.
TV> (defun epg-delete-output-file (context)
TV> "Delete the output file of CONTEXT."
TV> (let ((delete-by-moving-to-trash nil))
TV> (when (and (epg-context-output-file context)
TV> (file-exists-p (epg-context-output-file context)))
TV> (delete-file (epg-context-output-file context)))))
TV> With this change, data in clear text will never go to trash.
According to the docs for `delete-file' it shouldn't matter what
`delete-by-moving-to-trash' says because this is called
non-interactively (TRASH is nil when delete-file is called
non-interactively). Or is this funcall interactive somehow?
Ted
next prev parent reply other threads:[~2011-02-11 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 7:29 bug: epg send unencrypted data in trash Thierry Volpiatto
2011-02-11 18:16 ` Thierry Volpiatto
2011-02-11 19:54 ` Ted Zlatanov [this message]
2011-02-11 21:05 ` Thierry Volpiatto
2011-02-11 22:14 ` Ted Zlatanov
2011-02-12 0:23 ` Chong Yidong
2011-02-12 7:08 ` Thierry Volpiatto
2011-02-12 12:56 ` Ted Zlatanov
2011-02-12 18:49 ` Chong Yidong
2011-02-12 19:06 ` Ted Zlatanov
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sjvuxs80.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.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://git.savannah.gnu.org/cgit/emacs.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).