[1991] in linux-security and linux-alert archive
[linux-security] Re: Chrooting bind 8.1.2 under debian 2.0
daemon@ATHENA.MIT.EDU (Petri Kaukasoina)
Fri Jul 17 08:58:53 1998
Date: Fri, 17 Jul 1998 13:17:00 +0300
From: Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi>
To: linux-security@redhat.com
Mail-Followup-To: linux-security@redhat.com
In-Reply-To: <Pine.LNX.3.96.980717110508.29168A-100000@lost.data.ee>; from Cougar on Fri, Jul 17, 1998 at 11:30:32AM +0300
Resent-From: linux-security@redhat.com
Resent-Reply-To: linux-security@redhat.com
On Fri, Jul 17, 1998 at 11:30:32AM +0300, Cougar wrote:
> My idea is to run named non-root UID/GID. As named needs to bind port 53
> which is below 1024 there are problem to execute it.
To run named from bind-8.1.2 with UID 123 and GID 456:
named -u 123 -g 456
To run it chrooted under /var/named with UID 123 and GID 456:
named -t /var/named -u 123 -g 456
--
----------------------------------------------------------------------
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
