Date: Wed, 20 Nov 1996 10:22:03 -0800 From: Paul Traina <pst@shockwave.com> To: Tom Fischer <tfischer@panoramix.rain.fr> Cc: freebsd-security@freebsd.org Subject: Re: Serious BIND resolver problem. (fwd) Message-ID: <199611201822.KAA21077@precipice.shockwave.com> In-Reply-To: Your message of "Wed, 20 Nov 1996 18:15:55 GMT." <32934ADB.15FB7483@panoramix.rain.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Tom Fischer <tfischer@panoramix.rain.fr> Subject: Re: Serious BIND resolver problem. (fwd) Hello, Paul Traina warned: > If you're running 2.1R, you've got so many bloody security holes it's > not funny. If you allow "untrusted" users on your machine, my advice > is to upgrade to 2.1.6 or 2.1-stable (nearly the same thing) without delay. thanks for the advice, but I was hoping to delay this until 2.2R came out (in two months, supposedly). The security holes that I know about, and did something about are: mount_union, mount_msdos, man... suidperl iijppp rdist... Aside from this new libc thing, you're telling me that there are others as well? Is there an easy way to fix the libc problem while I wait for 2.2R? Upgrade to 2.1.6's libc. thanks, tom tfischer@rain.fr
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611201822.KAA21077>