This may be a time when you might actually want to consider running SSH chrooted. You could simply restrict what binaries are in the chrooted directory.
http://www.ssh.com/support/faq/secureshellserver/qa_191_687.html On Thu, 2002-12-12 at 11:08, Charles Farinella wrote: > On Thu, 12 Dec 2002 [EMAIL PROTECTED] wrote: > > > On Thu, 12 Dec 2002, at 10:06am, [EMAIL PROTECTED] wrote: > > > I think I've solved my problem by removing the path statement from > > > .bash_profile for the user in question, so that we can scp files to the > > > account, but the user can run no commands. > > > > If the user specifies the exact path to the command, it will still work. > > > > For example, > > > > ssh foo@bar /bin/sh > > > > would give them a shell prompt. > > I was doing so well....... :-( > > Ok, that won't work. I need to scp files to the machine, yet not allow > the user to execute anything. Any suggestions? > > --charlie > > -- > ------------------------------------------------------------------------ > Charlie Farinella, Appropriate Solutions, Inc. > [EMAIL PROTECTED] > 603-924-6079 > > > _______________________________________________ > gnhlug-discuss mailing list > [EMAIL PROTECTED] > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss _______________________________________________ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
