From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] DNSSec talk writeup from linuxcon
Date: Fri, 12 Oct 2012 12:00:11 -0700 [thread overview]
Message-ID: <CAA93jw6AouiNf7JmiN5y=q5ZKcfvJdFqTG5cCeDbyoLQbKC3MA@mail.gmail.com> (raw)
I've been sort of forwarding progress on various topics to the list
the past couple days
http://lwn.net/Articles/516797/
I note that after 5 CVEs this year, and the memory issues we've run
into, I've given up on the idea of shipping bind burned into flash by
default.
Simon Kelly of dnsmasq intends to explore what it will take to add a
lightweight dnssec implementaton of dnssec into dnsmasq over the
winter. If anyone is interested in helping pull that together let me
and he know.
Some funding may be available via some group who's url I forget right now.
I have some hope for the upcoming mdns/dns work to have a more merged
solution to some of the integration of naming and address assignment.
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
reply other threads:[~2012-10-12 19:00 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
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='CAA93jw6AouiNf7JmiN5y=q5ZKcfvJdFqTG5cCeDbyoLQbKC3MA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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