Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

RE: Restrict commands for all users

Subject: RE: Restrict commands for all users
Date: Mon, 16 Aug 2004 09:56:09 -0500
This is not advised... Using an executable as a shell that is not
intended as a shell is dangerous. You have to worry about traps and
whatnot. Things become exploitable when this is done.

I would suggest looking into the command="" option for the public key
(OpenSSH). This will allow you to execute a command once the user has
authenticated (depending on your auth options). I know SSH.com has a
similar function to execute a command, but who uses SSH.com?!? :)


-Carl

-----Original Message-----
From: Chris Jensen [mailto:cjensen@gmail.com] 
Sent: Thursday, August 12, 2004 3:20 AM
To: secureshell@securityfocus.com
Subject: Re: Restrict commands for all users

Have you tried to just change their login shell to "/usr/bin/unison" ?
I was under the impression (from reading other posts) that this isn't
a secure solution as it is possible for the client to request an
alternate shell


<Prev in Thread] Current Thread [Next in Thread>