On Thu, 21 Nov 2002, Ed Wilts wrote:

> On Thu, Nov 21, 2002 at 07:02:27PM -0500, Steve Howard wrote:
> > Can I set an upper level directory, /home/user, for example for each
> > user? I have been able to do this with ftp, but can I do it with ssh?
> 
> You mean you want to chroot the user so that they can't transfer files
> outside of that directory?  If so, the answer is no, openssh does not
> support this.  Any user that has ssh access to your system (or sftp via
> the openssh server) has regular access to every file, including your world
> readable password file.  This limitation is why I claim that ftp is

ehhh? If you don't trust them, keep them off your hosts.  If
you can't keep them off a host you admin, don't keep anything
on _that_  host or in that network segment you wouldn't share 
freely.  

Wrapper relentlessly. tripwire.  syslog the heck out of it to
a separate loghost; remove binaries which you can; trap the
others so that alarms go off on access out of the chroot; once
tripped, lock the account, pending termination as a violation
of the AUP.

And remember that there is always some local exploit you've
not heard of, so run it down an isolated P-t-P with full
coverage 'shadow' logging and 'snort' analysis.  Pay attention 
with logwatch and other reduction tools.

Failing that, the restricted shell approaches might help.  
These come to mind.  

Restricted bourne SHell: (man -s 1m rsh)
Restricted ksh (rksh)
chroot
pdksh (Public Domain Korn Shell) available from 
    http://www.cs.mun.ca/~michael/pdksh/
rbash

http://online.securityfocus.com/infocus/1575
http://www.ssh.com/support/faq/secureshellserver/qa_191_687.html
http://www.carcosa.net/jason/software/utilities/uchroot/readme.html

-- Russ Herrold



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to