From: "Eric S. Johansson" <esj@eggo.org>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] bash exploit heads up
Date: Wed, 24 Sep 2014 18:00:34 -0400 [thread overview]
Message-ID: <54233F02.4060603@eggo.org> (raw)
In-Reply-To: <54233DB3.4020602@eggo.org>
On 9/24/2014 5:54 PM, Eric S. Johansson wrote:
>
> On 9/24/2014 5:45 PM, Dave Taht wrote:
>> shows vulnerable for bash, not sh, on openwrt and cerowrt. That said,
>> it makes me nervous. I've never really liked the redir.sh method cero
>> uses to bounce people to the right web interface... suggestions to do
>> it in javascript or something safer desired.
>>
>
> http://www.w3.org/QA/Tips/reback
>
> I'll take a look in the next couple of days if no one beats me to it.
looked a bit further. assuming you are still using lighthttpd, it looks
like we should be able to to it from the lighthttp config
http://redmine.lighttpd.net/projects/1/wiki/docs_modredirect
prev parent reply other threads:[~2014-09-24 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 21:45 Dave Taht
2014-09-24 21:51 ` Toke Høiland-Jørgensen
2014-09-24 21:54 ` Eric S. Johansson
2014-09-24 22:00 ` Eric S. Johansson [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54233F02.4060603@eggo.org \
--to=esj@eggo.org \
--cc=cerowrt-devel@lists.bufferbloat.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