From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: bind vulnerability patched in cerowrt tree
Date: Thu, 17 Nov 2011 16:55:33 +0100 [thread overview]
Message-ID: <CAA93jw6ZcXoQhkS2z7vSPg4vV-t=kOPT3_dh6H6LdXE093UFKw@mail.gmail.com> (raw)
1) There is a fairly gnarly bind9 bug going around.
http://isc.sans.edu/diary.html?storyid=12049&rss
Regrettably I'm not in a position to make binaries for the lastest smoketest.
However updated sources are in the ceropackages repository. For those of you
doing your own builds, that would be something like
cd your_ceropackages_repo
git pull
cd ../your_cerowrt_dir
./scripts/feeds update cero
make package/bind-latest-server/{clean,compile,install}
2) In fact, I was just about to abandon the rc7-smoketest series entirely.
... and go to rc8. 'rc' is getting to be a misnomer...
A core goal was to get to where debloat-testing and cerowrt were
basically the same kernel,
and to stay within 2 kernel revision cycles. We're slipped past that.
rc8 has a pile O patches in it, notably linux 3.1.1, a new dropbear,
portions of debloat-testing,
another packet scheduler, a fix (I hope!) for the wifi detection
problem, dhcpv6, I forget
what else...
and I was about to fold some stuff from petri in there, and, well,
then item 1 cropped up.
3) I've been reflecting on what it takes to harden 'the front door' to a home.
It's not just limited to vulnerabilities to one daemon.
The simplest thing to do about that would be to buy some fishing gear,
and find a deserted
tropic island somewhere lacking in technology entirely. But then there
might be cannibals.
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
FR Tel: 0638645374
http://www.bufferbloat.net
reply other threads:[~2011-11-17 15:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw6ZcXoQhkS2z7vSPg4vV-t=kOPT3_dh6H6LdXE093UFKw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@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