From: David Aguilar <davvid@gmail.com>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: [PATCH] gitk: use mktemp -d to avoid predictable temporary directories
Date: Fri, 13 Jun 2014 14:43:48 -0700 [thread overview]
Message-ID: <1402695828-91537-1-git-send-email-davvid@gmail.com> (raw)
gitk uses a predictable ".gitk-tmp.$PID" pattern when generating
a temporary directory.
Use "mktemp -d .gitk-tmp.XXXXXX" to harden gitk against someone
seeding /tmp with files matching the pid pattern.
Signed-off-by: David Aguilar <davvid@gmail.com>
---
This issue was brought up during the first review of the previous patch
back in 2009.
http://thread.gmane.org/gmane.comp.version-control.git/132609/focus=132748
This is really [PATCH 2/2] and should be applied on top of my previous
gitk patch.
gitk | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gitk b/gitk
index 82293dd..dd2ff63 100755
--- a/gitk
+++ b/gitk
@@ -3502,7 +3502,8 @@ proc gitknewtmpdir {} {
} else {
set tmpdir $gitdir
}
- set gitktmpdir [file join $tmpdir [format ".gitk-tmp.%s" [pid]]]
+ set gitktmpformat [file join $tmpdir ".gitk-tmp.XXXXXX"]
+ set gitktmpdir [exec mktemp -d $gitktmpformat]
if {[catch {file mkdir $gitktmpdir} err]} {
error_popup "[mc "Error creating temporary directory %s:" $gitktmpdir] $err"
unset gitktmpdir
--
2.0.0.257.g75cc6c6
next reply other threads:[~2014-06-13 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 21:43 David Aguilar [this message]
2014-06-15 4:57 ` [PATCH] gitk: use mktemp -d to avoid predictable temporary directories Paul Mackerras
2014-06-15 7:51 ` Pat Thoyts
2014-06-15 16:32 ` brian m. carlson
2014-06-15 21:49 ` David Aguilar
2014-06-15 22:16 ` brian m. carlson
2014-06-16 18:17 ` Junio C Hamano
2014-06-19 2:54 ` David Aguilar
2014-06-16 11:40 ` Thomas Braun
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1402695828-91537-1-git-send-email-davvid@gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.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.
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 NNTP newsgroup(s).