Says it all really. That last BIND exploit supposedly gave you root access didn't it? Can someone explain to me how that can be when named runs as an unpriviledge usercode from within a chroot'ed jail? I mean I assume that's how 99% of us run BIND? :-| If it "somehow" got around even that level of protection, would have running it via "/sbin/chroot xxx named -u username" given more protection? There have been occasions in the past of mis-coded chroot support in apps... -- Cheers Jason Haar Unix/Special Projects, Trimble NZ Phone: +64 3 9635 377 Fax: +64 3 9635 417 - [To unsubscribe, send mail to [EMAIL PROTECTED] with "unsubscribe firewalls" in the body of the message.]
