Going backwards?

Yarin yarin at warpmail.net
Tue Feb 1 16:50:06 EST 2011


Thanks for clearing that up.

>> 1.4: The "legacy" branch of MaraDNS ... Has both the deprecated
>> MaraDNS 1.x recursive resolver and Deadwood

In this case, will compiling MaraDNS with --authonly produce the same
thing as compiling the 2.0 branch MaraDNS?


----- Original message -----
From: "Sam Trenholme" <strenholme.usenet at gmail.com>
To: list at maradns.org
Date: Mon, 31 Jan 2011 22:04:40 -0700
Subject: Re: Going backwards?

> Forgive me for my ignorance if I'm making a stupid mistake, but,
> what happened to the version numbers?

I have not made a new release of MaraDNS 2.0 yet. Yarin has
contributed a number of patches, and I would like to integrate his
patches before making a new MaraDNS 2.0 release; MaraDNS 2.0 users can
use the supplied patch.

Here are the three maintained branches of MaraDNS:

1.3: A deprecated branch; only maintained with security fixes and only
until December 21, 2012.  Distributed as source code.  Has only the
deprecated MaraDNS 1.x recursive resolver.

1.4: The "legacy" branch of MaraDNS; I still maintain this branch with
security and other bug fixes for the foreseeable future.  Distributed
as source code and as a Windows binary.  Has both the deprecated
MaraDNS 1.x recursive resolver and Deadwood (so people can slowly make
the transition to the new recursor)

2.0: The present branch of MaraDNS.  The legacy recursive code is
completely removed and replaced with Deadwood.  Distributed only as
source code.

Since MaraDNS 1.4 presently has all of the features MaraDNS 2.0 has
(but this will change when I get a chance to integrate your patches),
and since the exploit in question was a 0-day exploit, I plain simply
did not have time to make a release of all three branches of MaraDNS
to patch the exploit.  It didn't help that Valgrind was giving me
false alarms about memory leaks in Deadwood, and I had to spend time
verifying the reports were false alarms (if Valgrind says the memory
is "possibly lost", it can be a false alarm).

I will release 2.0 again in the next week or two, integrating Yarin's
patches in this release.

- Sam



More information about the list mailing list