Re: how to limit area's users can traverse

2000-07-23 Thread Helber
essage # Limit WRITE everywhere in the anonymous chroot DenyAll -Mensagem Original- De: John F. Davis <[EMAIL PROTECTED]> Para: debian isp mailing list Enviada em: Terça-feira, 18 de Julho de 2000 17:11 Assunto: how to limit area's users can traverse > hello > &

Re: how to limit area's users can traverse

2000-07-23 Thread Helber
essage # Limit WRITE everywhere in the anonymous chroot DenyAll -Mensagem Original- De: John F. Davis <[EMAIL PROTECTED]> Para: debian isp mailing list <[EMAIL PROTECTED]> Enviada em: Terça-feira, 18 de Julho de 2000 17:11 Assunto: how to limit area's users ca

Re: how to limit area's users can traverse

2000-07-19 Thread Chris Wagner
Just use group permissions. Put each user in their own group. Take away world access. chmod w-rwx * At 03:11 PM 7/18/00 -0500, John F. Davis wrote: >hello > >How do you limit the area which a user can go with ftp? >i.e, when user ftp's to my server, how do I keep him in >his portion of the file

Re: how to limit area's users can traverse

2000-07-19 Thread Chris Wagner
Just use group permissions. Put each user in their own group. Take away world access. chmod w-rwx * At 03:11 PM 7/18/00 -0500, John F. Davis wrote: >hello > >How do you limit the area which a user can go with ftp? >i.e, when user ftp's to my server, how do I keep him in >his portion of the fil

how to limit area's users can traverse

2000-07-18 Thread John F. Davis
hello How do you limit the area which a user can go with ftp? i.e, when user ftp's to my server, how do I keep him in his portion of the filesystem only. Way back when, I saw a setup on a redhat system which had a non standard "cd" binary which was put in each user's path. This "cd" could not be

how to limit area's users can traverse

2000-07-18 Thread John F. Davis
hello How do you limit the area which a user can go with ftp? i.e, when user ftp's to my server, how do I keep him in his portion of the filesystem only. Way back when, I saw a setup on a redhat system which had a non standard "cd" binary which was put in each user's path. This "cd" could not b