From owner-freebsd-security Tue Nov 23 15: 4:15 1999 Delivered-To: freebsd-security@freebsd.org Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (Postfix) with ESMTP id D0F8815254; Tue, 23 Nov 1999 15:04:06 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-mdt.sentex.net [205.211.164.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id SAA21030; Tue, 23 Nov 1999 18:02:07 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.1.19991123175926.04d892f0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 23 Nov 1999 18:02:05 -0500 To: Vlad Skvortsov , freebsd-security@FreeBSD.ORG From: Mike Tancsa Subject: Re: bind vulnerabilities Cc: current@FreeBSD.ORG In-Reply-To: <19991123235738.D595@high.net.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 03:57 PM 11/23/99 , Vlad Skvortsov wrote: > Sorry for probably a bit stupid question (I've been out of lists for > a while). Are patches for named already in -current or -stable ? > No they have not to either. Use it out of the ports. Be sure to adjust named-xfer "/usr/local/libexec/named-xfer"; // _PATH_XFER accordingly in your named.conf file. This raises a question, why has the new BIND not been committed to current at least ? I am not complaining, just curious as to the rationale ? ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 519 651 3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message