Re: Chrooted telnet support in 4.x???

2000-03-22 Thread Poul-Henning Kamp


You could do that, rather easily.

In message <[EMAIL PROTECTED]>, "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$[EMAIL PROTECTED]>, "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
>> [EMAIL PROTECTED]   "Real hackers run -current on their laptop."
>> FreeBSD -- It will take a long time before progress goes too far!
>> 
>> 
>> To Unsubscribe: send mail to [EMAIL PROTECTED]
>> with "unsubscribe freebsd-current" in the body of the message
>> 
>
>

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Chrooted telnet support in 4.x???

2000-03-22 Thread Mr. K.

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$[EMAIL PROTECTED]>, "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
> [EMAIL PROTECTED]   "Real hackers run -current on their laptop."
> FreeBSD -- It will take a long time before progress goes too far!
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



RE: Chrooted telnet support in 4.x???

2000-03-22 Thread Alejandro Ramirez

Thanks a lot for clarifying my mind,

I will take a look at this.

Greetings...
Ales

- Original Message -
From: Poul-Henning Kamp <[EMAIL PROTECTED]>
To: Alejandro Ramirez <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, March 22, 2000 12:40 PM
Subject: Re: Chrooted telnet support in 4.x???


> In message <051001bf942c$87e3fa40$[EMAIL PROTECTED]>, "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
> [EMAIL PROTECTED]   "Real hackers run -current on their laptop."
> FreeBSD -- It will take a long time before progress goes too far!
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Chrooted telnet support in 4.x???

2000-03-22 Thread Poul-Henning Kamp

In message <051001bf942c$87e3fa40$[EMAIL PROTECTED]>, "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
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message