From owner-freebsd-current Wed Mar 22 10:57:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 6E25837BF3A for ; Wed, 22 Mar 2000 10:56:54 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id TAA33115; Wed, 22 Mar 2000 19:56:25 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Mr. K." Cc: Alejandro Ramirez , freebsd-current@FreeBSD.ORG Subject: Re: Chrooted telnet support in 4.x??? In-reply-to: Your message of "Wed, 22 Mar 2000 13:55:33 EST." Date: Wed, 22 Mar 2000 19:56:25 +0100 Message-ID: <33113.953751385@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You could do that, rather easily. In message , "Mr. K." writes : >what would be even cooler is if we could jail() a user natively at >login. I bet this patch could be easily modified to use jail() instead of >chroot(). > >On Wed, 22 Mar 2000, Poul-Henning Kamp wrote: > >> In message <051001bf942c$87e3fa40$020a0a0a@megared.net.mx>, "Alejandro Ramirez" >> writes: >> >Hi, >> > >> >Will FreeBSD 4.x will be able to chroot telnet sessions natively???, or are >> >there any plans to integrate this patches to the base system: >> >> Investigate the jail(8) facility in 4.x, it is *far* stronger than >> anything chroot(2) has to offer. >> >> -- >> Poul-Henning Kamp FreeBSD coreteam member >> phk@FreeBSD.ORG "Real hackers run -current on their laptop." >> FreeBSD -- It will take a long time before progress goes too far! >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> > > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message