OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: Last DNS Fix available. But where?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Last DNS Fix available. But where?

  • To: NTBUGTRAQLISTSERV.NTBUGTRAQ.COM
  • Subject: Re: Last DNS Fix available. But where?
  • From: Paul Leach <paulleMICROSOFT.COM>
  • Date: Thu, 9 Apr 1998 12:04:17 -0700
  • Comments: To: Russ <Russ.CooperRC.ON.CA>
  • Reply-To: Paul Leach <paulleMICROSOFT.COM>
  • Sender: Windows NT BugTraq Mailing List <NTBUGTRAQLISTSERV.NTBUGTRAQ.COM>
The fix hasn't been widely released because it just isn't ready for
widespread public release. This is one of those cases where even the
disclaimer about lack of regression testing isn't strong enough, and PSS
involvement is really needed (as Russ notes).

We are working on getting it ready for general release.  In the meantime, if
you feel you are really at risk, call PSS.

It will be out before SP4.

Paul

> -----Original Message-----
> From: Russ [mailto:Russ.CooperRC.ON.CA]
> Sent: Wednesday, April 08, 1998 11:35 AM
> To: NTBUGTRAQLISTSERV.NTBUGTRAQ.COM
> Subject: Re: Last DNS Fix available. But where?
>
>
> >Can anybody point to me where to find this latest fix? Maybe MS
> >forgot to make it really available?
>
> As usual, lots of folks replied with lots of good answers.
>
> Basically, to get a fix that is not available from the standard MS FTP
> site, you need to contact Microsoft Professional Support Services (PSS)
> and refer to the KB article. MS typically do this when they feel the fix
> will cause additional support problems if widely distributed without PSS
> involvement (if they don't get a chance to determine whether you are
> going to be adversely affected by the fix, they'll get a call later
> saying its caused more problems than its solved).
>
> This is all well and good, but the reason I let this message through is
> because many of the issues addressed by this fix are very security
> related. Just the fact that DNS Cache Poisoning, for example, has been
> fixed is one excellent reason to get this fix applied to
> anyone who runs an NT DNS.
>
> http://support.microsoft.com/support/kb/articles/q159/3/10.asp
>  explains numerous fixes, enhancements, etc... to NT DNS that should be
readily
> adopted.
>
> No doubt they are leery about releasing increased functionality within a
> Hot Fix, but I have to stress that this fix would seem to represent an
> excellent combination of increased functionality and bug fixes related
> to security-sensitive sites.
>
> So this is my call on Microsoft to make this HF available through normal
> HF channels, or give us a good reason why its not. Since we still do not
> have a date for SP4, it should be safe to say that this HF will have
> sufficient life in it to bring some peace of mind to users of NT DNS.
>
> Cheers,
> Russ - NTBugtraq moderator
> http://www.ntbugtraq.com/ntbugfaq.htm for posting guidelines.
>