[1844] in linux-security and linux-alert archive

home help back first fref pref prev next nref lref last post

[linux-security] http://www.seifried.org/dns/index.html - BIND chrooted() instructions

daemon@ATHENA.MIT.EDU (seifried@seifried.org)
Tue Jun 9 07:01:12 1998

Date: Tue, 9 Jun 1998 01:48:24 -0600 (MDT)
From: <seifried@seifried.org>
To: linux-security@redhat.com
In-Reply-To: <Pine.LNX.3.96.980606123543.2899A-100000@dolemite.psionic.com>
Resent-From: linux-security@redhat.com
Reply-To: linux-security@redhat.com

> Hello,
> 
> I traditionally have always run BIND in a chroot() environment and always
> recommend admins do the same because this program is rather complicated in
> it's functionality. This can provide a high degree of protection from a
> lot of nonsense that a person may wish to throw at you.

psionics was not responding <at least for me> so I wrote a set of
instructions on how to setup BIND for a chrooted environment in RedHat
5.X.

http://www.seifried.org/dns/index.html

Pretty much step by step instructions, it's what I have been using for
a while. 

-seifried

P.S. feedback/constructive criticism is appreciated, I am considering
writing a series of 'articles' on securing RedHat servers, if you are
interested please encourage me ;)

-- 
----------------------------------------------------------------------
Please refer to the information about this list as well as general
information about Linux security at http://www.aoy.com/Linux/Security.
----------------------------------------------------------------------

To unsubscribe:
  mail -s unsubscribe linux-security-request@redhat.com < /dev/null


home help back first fref pref prev next nref lref last post