[MaraDNS list] Deadwood update; Deadwood 2 and MaraDNS 1 end-of-life

Sam Trenholme <[email protected]> Fri, 21 Jun 2013 14:35:35 -0700
Newsgroups gmane.network.dns.maradns.general
Message-ID <CAJxgfkSMbQaqmNSCyJjMzHaSmjzBV0cO4gXMGxZTESUc6+=WWA@mail.gmail.com>
11 years ago today, I released MaraDNS 1.0 to the world. Today, I have
updated Deadwood and am announcing another end-of-life.

=3D=3DDeadwood update=3D=3D

I have added a FAQ entry about using Deadwood with RFC1918 addresses.

It can be downloaded here:

 http://www.maradns.org/deadwood/snap/

The updated FAQ:

 http://maradns.org/deadwood/doc/FAQ.html#11

=3D=3DDeadwood 2.0 end-of-life=3D=3D

I have dropped most support for the older, more compact Deadwood 2.0
release. The only thing I update in this branch of Deadwood is
security holes with CVE numbers.

The last update to Deadwood 2.0 was Deadwood 2.3.08, which addressed
CVE-2012-1570.

I am now placing an end of life on Deadwood 2.0: June 21, 2016. This
gives users three years to update to Deadwood 3.0. With Deadwood out
for over two years, it=92s time to upgrade.

=3D=3DMaraDNS 1 end-of-life=3D=3D

Please remember that all MaraDNS 1 releases are only supported for CVE
security holes, and that this branch of MaraDNS will no longer be
supported two years from today (June 21, 2015):

 http://samiam.org/blog/20120621.html

=3D=3DCurrent MaraDNS plans=3D=3D

Unless a CVE security hole comes up, my present plan is to release
Deadwood 3.2.04 and MaraDNS 2.0.08 sometime around the end of the
year.

While not a hard-and-fast rule (for example, I answered a lot of email
on the list this month), my plan is to work on MaraDNS or Deadwood
again one day in a couple of months unless a critical security bug
with a CVE number is found.