From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: difflog.pl and "security"
Date: Mon, 3 Dec 2007 17:36:37 +0000 [thread overview]
Message-ID: <20071203173637.4233d948@news01> (raw)
In-Reply-To: <071203083301.ZM4267@torch.brasslantern.com>
On Mon, 03 Dec 2007 08:33:01 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Dec 3, 10:42am, Peter Stephenson wrote:
> }
> } Yes, I'm more worried about the implication that anything distributed
> } will be assumed to be robust for any usage. In the usage for which
> } difflog.pl is supplied, security is not an issue since you're diffing
> } two publicly available logs.
>
> If I understand the issue correctly, the problem is not what's in the
> log files, but what's in /tmp.
>
> E.g., if a local attacker can guess when difflog.pl is being run and
> what its process ID is, he can create symlinks in /tmp that point
> from the files difflog is about to create, to any files owned by the
> person running difflog, and cause the target files to be clobbered.
Yes, you're right. However, the other remark stands... should I commit
the change I suggested? (There's obviously no harm in the documentation
update.)
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
next prev parent reply other threads:[~2007-12-03 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 21:40 Clint Adams
2007-12-03 1:45 ` Bart Schaefer
2007-12-03 10:42 ` Peter Stephenson
2007-12-03 16:33 ` Bart Schaefer
2007-12-03 17:36 ` Peter Stephenson [this message]
2007-12-03 18:37 ` Bart Schaefer
2007-12-03 21:36 ` Wayne Davison
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=20071203173637.4233d948@news01 \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/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.vuxu.org/mirror/zsh/
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).