RedHat did a back port of the random port fix into the official RHEL repositories.
On my RHEL 5 I'm running their back ported 9.3.4-P1 and it is doing port randomization just fine. All I had to do with the "yum update" for bind (bind-chroot in my case) then insure I didn't have query port restriction in named.conf. http://rhn.redhat.com/errata/RHSA-2008-0533.html -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Res Sent: Tuesday, August 12, 2008 10:31 PM To: jri Cc: [email protected] Subject: Re: How to patch Fedora Core 2 Bind RPM? On Tue, 12 Aug 2008, jri wrote: > What about Redhat? we are using paid redhat enterprise version, but > they are still with the version 9.3 and no P2 yet (9.3.4-6.0.2.P1 > available on july 10). > So end up compiling is not what I thought when buying RHEL. > Any comments will be appreciated. Simple, take it up with RedHat, its got nothing to do with ISC, that they and debian and so on have policies about living in dark ages, but then, you should be aware of this if you use their distros anyway to make for these allowances, research a bit more before using those types of distros. The only Linux flavours that keep complete up to date are the ones that use upstream sources (like ISC's bind), Slackware (and I heard Gentoo) do this. (PS: fanbois of RH/Debian/Ubunut/CentOS/insert_other_variant_here please dont waste your time with the rhetoric we get about "stableness" and only why back patch security blah blah blah, if I hear that crap once more I'll throw up, its old, its boring, if the likes of Slackware can produce a completely stable and bullet proof distro for well over a decade no reason others cant) Res (a RHEL'r as well as a Slackware'r) ---------------------------------- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. ----------------------------------
