From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Cc: shawn wilson <ag4ve.us@gmail.com>
Subject: Re: zsh 5.0.7 released
Date: Thu, 09 Oct 2014 18:54:17 -0700 [thread overview]
Message-ID: <141009185417.ZM29893@torch.brasslantern.com> (raw)
In-Reply-To: <CAH_OBicE38Mj6FW=1bbXMH7YZWNb0FRsPUM9wEPtKQe+3Z-V3A@mail.gmail.com>
On Oct 9, 6:41pm, shawn wilson wrote:
}
} > > > privilege escalation, under some specific and atypical conditions
} > > > where zsh is being invoked in privilege elevation contexts when the
} > > > environment has not been properly sanitized, such as when zsh is
} > > > invoked by sudo on systems where "env_reset" has been disabled.
} > >
} > > Was this security issue in SSH discussed on the list somewhere (I can't
}
} s/SSH/bash/
Did you mean zsh instead of bash?
} > > seem to find other mention of it outside the readme - not even direct
} > > mention in changelog or git log)...?
}
} And I was referring to the zsh readme, changelog, git log.
The paragraph about "privilege escalation" quoted above appears at the
top of the README file.
Change log entry is this:
2014-09-29 Peter Stephenson <p.stephenson@samsung.com>
* users/19183: Src/hist.c: handle unlikely error case with
fdopen() better.
* 33276: Src/params.c, Src/zsh.h: safer import of numerical
variables from environment.
The git log is very brief and is the same as the 33276 ChangeLog.
} > I don't know of an ssh issue, but the sudo issue was discussed offline.
} >
} > The original point about sanitising integer imports, however, was
} discussed
} > here.
}
} Huh, I'll look again.
The first mention of the integer import problem on the list is here:
http://www.zsh.org/mla/workers/2014/msg01041.html
--
Barton E. Schaefer
next prev parent reply other threads:[~2014-10-10 1:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141008193835.5d66c0ad@pws-pc.ntlworld.com>
[not found] ` <CAH_OBieFY24--_Ka637pM0g-iKEKLrnz4zXLcWKj9_mx+DKn=w@mail.gmail.com>
2014-10-09 20:48 ` Peter Stephenson
2014-10-09 22:41 ` shawn wilson
2014-10-10 1:54 ` Bart Schaefer [this message]
2014-10-11 22:53 ` shawn wilson
2014-10-11 0:18 ` Simon Ruderich
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=141009185417.ZM29893@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=ag4ve.us@gmail.com \
--cc=zsh-workers@zsh.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.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).