9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Kurt H Maier <khm@sciops.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] shell functions
Date: Fri, 26 Sep 2014 16:55:36 +0000	[thread overview]
Message-ID: <20140926165536.Horde.zSt4YsUnGF67-VxTNhnw9A3@ssl.eumx.net> (raw)
In-Reply-To: <CAJSxfmJziKuERcDs6H+6bs5CVjfNv_Ddq1vbo75eqiViQyXSCQ@mail.gmail.com>

Quoting Skip Tavakkolian <skip.tavakkolian@gmail.com>:

> you misrepresent. rsc addressed the non-web-centric issue:
>
>> I don't think it is super important to try to make rc defend against
> malicious environments, any more than
>> it is to make it somehow defend against malicious $paths. If those are
> security-relevant, you've already lost.

I misrepresent nothing, since I'm talking about what needs fixing in
bash.  I agree that rc doesn't need any patching -- to subvert rc like
this you need to be able to *name* the variables.  The problem with bash
is that it's not just HTTP_ variables, but ALL variables that contain () {
in them *anywhere*  get evaled in full.  Russ is advocating patching one
attack vector instead of fixing the actual problem, and I disagree about
that being a good idea.

khm




  reply	other threads:[~2014-09-26 16:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAL0h+tWUCrwWoTSeLz+Kx1yqKwKqwDBZZbH7fLe-PWXjLSgWWw@mail.gmail.com>
2014-09-26 15:54 ` Russ Cox
2014-09-26 16:32   ` [9fans] " Kurt H Maier
2014-09-26 16:44     ` Skip Tavakkolian
2014-09-26 16:55       ` Kurt H Maier [this message]
2014-09-29 15:30     ` Russ Cox
2014-09-26 16:48   ` Bakul Shah
2014-09-27 14:40   ` Christian Neukirchen
2014-09-28  7:00     ` arisawa
2014-09-28  9:39       ` Richard Miller
2014-09-29 13:03         ` arisawa
2014-09-29 13:20           ` Charles Forsyth
2014-10-01  9:37             ` arisawa
2014-09-29 18:05           ` erik quanstrom

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=20140926165536.Horde.zSt4YsUnGF67-VxTNhnw9A3@ssl.eumx.net \
    --to=khm@sciops.net \
    --cc=9fans@9fans.net \
    /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).