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. |

| Subject: | Re: Restrict commands for all users |
|---|---|
| Date: | Fri, 13 Aug 2004 09:26:42 +1000 |
On Thu, 12 Aug 2004 18:20:08 +1000, Chris Jensen <cjensen@gmail.com> wrote:
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
Also, wouldn't this mean that when the client end executes ssh user@server unison -arg1 -arg2 that the remote server would execute /usr/bin/unison unison -arg1 -arg2 (ie launch the shell, passing it the command to execute, and the arguments to that command, but as far as unison is concerned, the first argument is erronious.)
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | HELP please! Why is the agent NOT recognized, Christopher.Fouts |
|---|---|
| Next by Date: | PAM and password authentication, jniehof |
| Previous by Thread: | Re: Restrict commands for all users, Chris Jensen |
| Next by Thread: | RE: Restrict commands for all users, Turner, Carl H [NTK] |
| Indexes: | [Date] [Thread] [Top] [All Lists] |