unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r113773: Gnus: delete temporary files when Gnus exits instead of using timers
Date: Mon, 12 Aug 2013 15:20:51 +0200	[thread overview]
Message-ID: <m361vbm4ek.fsf@stories.gnus.org> (raw)
In-Reply-To: <b4m61vb200z.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 12 Aug 2013 10:03:24 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>> Yes.  Having the files in /tmp linger for a "long time" is not what
>> users expect, I think, and may lead to privacy problems.
>
> Yes, we should think much of privacy.  A better way would be to
> set $TMPDIR, $TEMP, $TMP, and so forth to someting like "~/tmp".

I think putting things in /tmp (under a subdirectory) is fine in
general.  There isn't much information leakage there -- the
subdirectories are created readable by the user only.

However, if these files linger on for months, then they may be picked up
by backup systems and the like, and that may not be what the user
expects.

-- 
(domestic pets only, the antidote for overdose, milk.)
  No Gnus T-Shirt for sale: http://ingebrigtsen.no/no.php
  and http://lars.ingebrigtsen.no/2013/08/twenty-years-of-september.html



      parent reply	other threads:[~2013-08-12 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1V7hi3-00028W-75@vcs.savannah.gnu.org>
2013-08-09 14:08 ` [Emacs-diffs] trunk r113773: Gnus: delete temporary files when Gnus exits instead of using timers Stefan Monnier
2013-08-09 23:16   ` Katsumi Yamaoka
2013-08-10  2:19     ` Stefan Monnier
2013-08-11 20:07       ` Lars Magne Ingebrigtsen
2013-08-12  1:03         ` Katsumi Yamaoka
2013-08-12  5:06           ` Achim Gratz
2013-08-12 13:20           ` Lars Magne Ingebrigtsen [this message]

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=m361vbm4ek.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=yamaoka@jpl.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).