[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

BIND 8.1.2-T3B and BIND 4.9.7-T1B



-----BEGIN PGP SIGNED MESSAGE-----


Announcing BIND 8.1.2-T3B.  If you are running BIND 8.1.1 or 8.1 you want to
upgrade.

Announcing BIND 4.9.7-T1B.  If you are still running BIND-4 rather than BIND-8,
you need the security patches contained herein.  But, you should really just
run BIND-8.  (See below for motivation.)

BIND is brought to you by the Internet Software Consortium, which provides
publically available references of key portions of Internet infrastructure.

The security fixes included in these releases fix a stack overrun that
could occur if inverse query support was enabled, and a number of
denial of service attacks where malformed packets could cause the
server to crash.

Both BIND 8.1.2-T3B and BIND 4.9.7-T1B are release candidates.  There will
be a brief public beta period to identify any remaining problems before
we release the final versions of BIND 8.1.2 and BIND 4.9.7.


BIND 8.1.2's changes from BIND 8.1.1 include:

	-> Improved security.
	-> Memory leaks have been plugged.
	-> Bug fixes.
	-> Updated ports, plus new ports for QNX, LynxOS, HP-UX 9.x, and
	   HP MPE.

See the README and CHANGES files in the BIND 8 source kit for full details.


BIND 4.9.7's changes from BIND 4.9.6 include:

	-> Improved security.
	-> Memory leaks have been plugged.

BIND 8's features over BIND 4 are too numerous to mention here, but they
include:

	-> DNS Dynamic Updates (RFC 2136).
	-> DNS Change Notification (RFC 1996).
	-> Completely new configuration syntax (and HTML docs for same).
	-> Flexible, categorized logging system (blackhole lame delegations!).
	-> IP-address-based access control for queries, zone transfers, and
	   updates that may be specified on a zone-by-zone basis.
	-> More efficient zone transfers (no fork() on outbound!).
	-> Improved performance for servers with thousands of zones.
	-> get*by*() functions can now use Sun NIS if desired/available.
	-> Many bug fixes, including patches for all known security holes.

The release files are:

BIND 8.1.2-T3B:

ftp://ftp.isc.org/isc/bind/src/testing/bind-src.tar.gz		source code
ftp://ftp.isc.org/isc/bind/src/testing/bind-src.tar.gz.asc	PGP sig
ftp://ftp.isc.org/isc/bind/src/testing/bind-doc.tar.gz		documentation
ftp://ftp.isc.org/isc/bind/src/testing/bind-doc.tar.gz.asc	PGP sig
ftp://ftp.isc.org/isc/bind/src/testing/bind-contrib.tar.gz	contributions
ftp://ftp.isc.org/isc/bind/src/testing/bind-contrib.tar.gz.asc	PGP sig

BIND 4.9.7-T1B:

ftp://ftp.isc.org/isc/bind/src/testing/bind-4.9.7-T1B.tar.gz	whole thing
ftp://ftp.isc.org/isc/bind/src/testing/bind-4.9.7-T1B.tar.gz.asc	PGP sig

The ".asc" files are PGP signatures for the kits, signed with the
<pgpkey@isc.org> key.  This key has been submitted to the MIT key ring with
a lot of well known signatures on it.  It can also be found at
<URL:http://www.isc.org/isc/> along with a lot of other ISC related
material that we hope you'll glance through.

Bugs may be reported by sending mail to <bind-bugs@isc.org>.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNSwDpm2DN4pRurLtAQHqXAP/crnnA1sajD51Cx8vAS8J8YC9iBVcErKu
AxcUMUScymwAlHKriLhNZmnB7823AtX0swlDrrBKMF3h89uUpRwAil1LdDz9YHSA
cgcxyYqWFor9lELMNz9CjA+veL2TAb1RSjOhlo221Fs3u4iMrW8DYd2+QaOjBeci
Qc+BWaEGGis=
=z2jk
-----END PGP SIGNATURE-----