ok i have this problem
i have created user marko
now his home dir is
/home/marko
and he has shell access

how can i disable him to go to dirs under /home/marko ???



thnx

This isent the answer you want, but it is the one everyone gets. Remove telnet and disable access

I would recommend disabling access also. However, you could change his shell to a restricted shell. But it all depends on what binaries he needs to use when logged in (ls, etc...). You could use bash -r as his shell. You will have to find out more to set this up. :(

I would also recommend using ssh rather than telnet.

Hope this helps,
Infinite ;)

yeah i am using ssh only i call that telnet
and i dont wont to disable shell acces to the users

bash -r how do i setup that ?
and page i could look about


thnx

There is no effective way to do that.
Not even disableing shell access.

What operating system. From my understanding, FreeBSD's Jail system allows funcionality like this.

"Jail, users with privilege find that the scope of their requests is limited to the jail, allowing system administrators to delegate management capabilities for each virtual machine environment"

http://docs.freebsd.org/44doc/papers/jail/jail.html

....

In the /etc/passwd file just change the ending of their line. You will see most say /bin/bash just change theirs to /bin/bash -r

then i cant log thru ssh at all with that username and password ....

What exactly do you need?

Regards

that user let's say marko has his home dir
/home/marko
and when he logs to his shell
he is unable to view files other
than
/home/marko and it's subdirectories ....



thnx

Originally posted by jizaymes
What operating system. From my understanding, FreeBSD's Jail system allows funcionality like this.

"Jail, users with privilege find that the scope of their requests is limited to the jail, allowing system administrators to delegate management capabilities for each virtual machine environment"

http://docs.freebsd.org/44doc/papers/jail/jail.html

I think this is also called a chroot'ed environment. chroot'ing is available in Linux.

domus,

If you are talking about a hosting company, then whatever you do there is no use. Anybody can set a CGI, PHP or SSI script to read any file readable by the Apache user (i.e.: all directories and pages of other users accessible through the web, including those that contain database passwords.)

This topic have been brought up here and elsewhere many times, but there is really no solution to this problem until today.

Sorry, repeated.