From: Glenn Morris <rgm@gnu.org>
To: Rob Browning <rlb@defaultvalue.org>
Cc: Steve Kemp <steve@steve.org.uk>, 17428@debbugs.gnu.org
Subject: bug#17428: Bug#747100: emacs23: Insecure use of temporary files in included lisp libraries/packages
Date: Tue, 06 May 2014 23:48:28 -0400 [thread overview]
Message-ID: <71mweul04z.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87r4466yxs.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Tue, 06 May 2014 22:38:07 -0500")
>> lisp/gnus/gnus-fun.el:
>> In the function `gnus-grab-cam-face` the file "/tmp/gnus.face.ppm" is
>> used, blindly allowing the existing file to be truncated, and symlinks
>> followed.
http://lists.gnu.org/archive/html/emacs-diffs/2014-05/msg00055.html
>> lisp/emacs-lisp/find-gc.el:
>> In the function `trace-call-tree` there are some horrific invocations
>> of the csh, which manipulate the directory and symlinks beneath "/tmp/esrc".
http://lists.gnu.org/archive/html/emacs-diffs/2014-05/msg00056.html
>> lisp/net/browse-url.el
>> In the function `browse-url-mosaic` the file "/tmp/Mosaic.$PID" is blindly
>> overwritten. Suspect this whole function is obsolete though :)
Not an (Emacs) bug.
http://lists.gnu.org/archive/html/emacs-diffs/2014-05/msg00057.html
>> lisp/net/tramp.el
>> The function `tramp-uudecode`, a fallback if a real uudecoding binary
>> is not present, blindly uses "/tmp/tramp.$PID", truncating and removing
>> the file.
http://lists.gnu.org/archive/html/emacs-diffs/2014-05/msg00060.html
next prev parent reply other threads:[~2014-05-07 3:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140505143834.GA5032@steve.org.uk>
2014-05-07 3:38 ` bug#17428: Bug#747100: emacs23: Insecure use of temporary files in included lisp libraries/packages Rob Browning
2014-05-07 3:48 ` Glenn Morris [this message]
2014-05-08 9:02 ` Steve Kemp
2014-05-08 9:03 ` Steve Kemp
[not found] ` <1399539828.22874.0@ssh>
2014-05-08 16:22 ` bug#17428: " Glenn Morris
2014-05-08 18:14 ` Glenn Morris
2014-05-08 16:34 ` Steve Kemp
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=71mweul04z.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=17428@debbugs.gnu.org \
--cc=rlb@defaultvalue.org \
--cc=steve@steve.org.uk \
/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).