maradns-2.0.05:
This is a stable release of MaraDNS.
* Security bugfix for CVE-2011-5056
* Deadwood updated to Deadwood 3.2.01
* Nicholas Bamber's Makefile.freebsd file added.
(2012.02.12)
maradns-1.4.10:
The hash compression function has better collision resistance.
More details at http://bam2.vk.tj
(2012.01.13)
maradns-1.4.09:
Hotfix: The hash randomization now has 31 bits of entropy, and
the hash does a fairly good job of choosing a random hash
bucket again. More details at http://al72.vk.tj
(2011.12.30)
maradns-1.4.08:
Security hotfix: Hash randomization added to MaraDNS 1's
recursive resolver. MaraDNS 2 is not impacted (it's been using
a randomized hash since 2007). More details at
http://al62.vk.tj
(2011.12.29)
maradns-1.4.07:
This is a legacy release of MaraDNS. All patches are backports
of MaraDNS 2.0 bug fixes.
* A typo fix for fetchzone
* AXFR-over-UDP packets are now correctly marked "truncated"
* It is now possible to have the '/' in hostnames
* Fix for Debian bug #607739: Hostname shown when
complaining about DDIP issues
* AngelD's issue with zone transfers when there are a lot of
FQDN4 records fixed.
* Karim's issue with '/read' directive fixed
(2011.11.11)
maradns-1.4.06:
This is the stable branch of MaraDNS.
* Fix for CVE-2011-0520
* Deadwood updated to 3.0.02
(2011.01.28)
maradns-1.4.05:
This is a stable branch of MaraDNS.
* Deadwood updated to the stable 3.0.01 release.
* MicroDNS now returns "not implemented" when given an EDNS packet
* FAQ updated.
(2010.09.25)
maradns-1.4.04:
This is the stable branch of MaraDNS.
* Bugfix: NAPTR records now work when ~ is used to separate
records
* NAPTR records now documented
* Bugfix: ANY queries now correctly work with NS referrals
* Example IPv6 addresses now use RFC-4193 compliant IPs
* Website updated to point out that Deadwood is now feature
complete and ready for beta-testing
* Some updates to the SQA regressions
* Deadwood updated to Deadwood 2.9.02
* Windows-only mkSecretTxt program added (*NIX users can
just type in "dd if=/dev/urandom of=secret.txt bs=64
count=1"; this gives Windows the same ability).
(2010.07.31)
changelog:
maradns-1.0.39:
* Backport of memory leak fix to 1.0 branch of MaraDNS
(2006.07.24)
maradns-1.0.38:
Backport of MaraDNS 1.2.09 Microsoft.com fix to legacy 1.0 branch
(2006.06.16)
maradns-1.0.37:
This is an update for the 1.0 legacy branch of MaraDNS
* Removed all example mararc files which allow any IP on the
internet to perform recursive queries (these can be used for
denial of service attacks)
(2006.04.07)
maradns-1.0.36:
This is a bugfix release for the legacy 1.0 branch of MaraDNS.
* A backport of the 2-line patch recently posted to the mailing
list concerning incorrect dangling CNAME warnings
(2005.12.31)
maradns-1.0.35:
* Backport of 1.1.x fix of csv1 example in documentation
* Backport of 1.1.x fix of MINFO RR description
* Backport of 1.1.x security fix.
(2005.11.20)
maradns-1.0.34:
* Hotfix: recursion works again
* Regression procedure added.
(2005.10.26)
maradns-1.0.33:
* Fixed occassional crash that happens while reading zone files at
MaraDNS startup.
* Fixed occassional compression error which shows up in MaraDNS
logs.
* Update man page to point out some unimplemented features will be
in 1.2
(2005.10.24)
maradns-1.0.32:
Hotfix: RR rotation now works again.
(2005.08.08)
maradns-1.0.31:
Two patches by Albert Lee that improve Maras stability.
(2005.08.07)
maradns-1.0.30:
* Warn the user when they have dangling CNAME records
* Fix bug with MX records with preferences > 255 in getzone tool
(2005.06.30)
maradns-1.0.29:
This release improves how MaraDNS'recursive resolver parses
packets so that Mara can interoperate better with some stub
resolvers that dont bother looking past the header of a DNS
packet.
(2005.05.13)
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
under share/examples/rc.d. The variable name already was named
RCD_SCRIPTS_EXAMPLEDIR.
This is from ideas from Greg Woods and others.
Also bumped PKGREVISION for all packages using RCD_SCRIPTS mechanism
(as requested by wiz).
automatically by pthread.buildlink3.mk. Also, factor out the pthread
library out of PTHREAD_LDFLAGS into a standalone variable PTHREAD_LIBS
and use it in packages where necessary (usually the ones that don't
have a GNU configure script).
o Fixes to make building and installing more easy
o Make MaraDNS actually look into ${PKG_SYSCONFDIR} for its configuration
file, thus bumping PKGREVISION.
(Note that anyway, maradns' installation process is screwed up. It uses
cp and mkdir to install things, it copies useless stuff like Makefiles,
installs duplicates of manpages, etc...)
Changes:
Cleaned up and fixed a bug in the MaraDNS startup
script. Now, the only prorcesses that will be killed
will be bona fide MaraDNS processes.
Closes PR pkg/22963.
Package provided by pancake <pancake@phreaker.net> via pkgsrc-wip.
MaraDNS is a package that implements the Domain Name Service (DNS), an
essential internet service. MaraDNS is intended for environments where a DNS
server must be secure and where the server must use the absolute minimum
number of resources possible. MaraDNS was created in response to issues
people had with the DNS servers available in early 2001; and has the
following design goals:
Security-aware programming. A DNS server needs to be secure. I have a number
of security features in the code, including:
1. The code uses a special string library which is resistant to buffer
overflows.
2. The code, if started as root, mandates running as an unpriviledged user
in a chroot() jail.
Open-Source. The 1.0 release of the DNS server is public-domain code;
the 1.2 release will be released under a very liberal BSD-style license.
Simplicity. This DNS server has the minimum number of features needed to
correctly act as an authoritative and/or recursive name server.
