Why not just download the -safe- bind source and compile it?
Or for that matter, just use rpm to remove the bind version he has now (he
has the 3.0.3 cd I asume in case this doesn't work -there's no reason it
wouldn't work-), then try out the redhat 4.2 bind rpms...as far I can tell
there are no package dependancies for bind and the 4.2 ones should work
just fine.
Dan
At 02:55 PM 5/22/98 -0400, Phil Garrett wrote:
>We've got a client who is severly attached to their 3.0.3 system. We've
>been trying for quite some time to convince them to upgrade to at least 4.2
>but so far no luck.
>
>With the recent named security holes, it looks like we may be able to
>convince them. Problem is, this is a very heavy use machine and we just
>can't bring it down to update it. Its going to at least another 3 weeks
>before we can upgrade them.
>
>Here's the problem... how do we protect them from the named security hole
>until then (short of disabling the named service which is not really an
>option).
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
