Bind-8.2.2 compile question

[Barry Margolin]

In article <Pine.LNX.4.20.0004291428060.14679-100000 at tartarus.netherrealm.net>,
Sheer El-Showk  <sheer at tartarus.netherrealm.net> wrote:
>Hi,
>
>I've recently upgraded some Linux systems from Bind-8.1.2 to Bind-8.2.2 by
>downloading the new source, compiling it in a seperate directory, shutting
>down the old bind version (/usr/sbin/ndc stop), and then doing a 'make
>install' in the new bind source directory.  Everything seems to be working
>fine, but I'm just worried that the bind install might not overwrite
>everything in the old install (I mean I'm sure I'm now running 8.2.2 -- I
>checked with nslookup, but I'm worried that files lying around from the
>old install might somehow pose a security hazard).  Is this the standard
>procedure for a bind upgrade?  Are there any security precautions I should
>take since the old version of bind had many known exploits and I never
>actually removed it?

There are only three files that should be installed: named, named-xfer, and
ndc.  If they were all updated, then nothing should be left from the old
version.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.