From: fair-tuhs@netbsd.org (Erik E. Fair)
Subject: [TUHS] Interesting post by Rob Pike in 1985: Shells, features and interaction
Date: Tue, 17 Nov 2015 17:56:28 -0800 [thread overview]
Message-ID: <7694.1447811788@cesium.clock.org> (raw)
In-Reply-To: <877flgw816.fsf@fastmail.com>
That function export feature of bash was not the cause of the
Shellshock vulnerability.
The cause was idiot programmers who wrote CGI scripts for bash
without proper data sanitization.
See also
https://www.quora.com/Are-there-any-projects-to-replace-bash-the-Unix-shell/answer/Erik-Fair
Erik <fair at netbsd.org>
next prev parent reply other threads:[~2015-11-18 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 22:55 Random832
2015-11-18 0:38 ` Random832
2015-11-18 0:50 ` Brantley Coile
2015-11-18 12:47 ` Christian Neukirchen
2015-11-18 1:56 ` Erik E. Fair [this message]
2015-11-18 5:15 ` Kurt H Maier
2015-11-18 5:36 ` Random832
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=7694.1447811788@cesium.clock.org \
--to=fair-tuhs@netbsd.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).