Secure Shell
ForceCommand executes shell Apr 19 2011 12:23PM
Walter de Jong (walter sara nl) (1 replies)
RE: ForceCommand executes shell Apr 20 2011 03:25PM
Males, Jess (jmales cio sc gov) (1 replies)
Re: ForceCommand executes shell Apr 21 2011 06:50AM
Walter de Jong (walter sara nl)
Hi,

This works, but ruins the possiblity of having a normal shell on the
standard port 22.

Another note, if you want the possibility of letting the user specify
any command-line arguments, oper-only-ever-gets-to-do-this.sh should
accept the '-c' argument as sshd executes 'shell' '-c'.

Something else, I noticed that an scp also triggers the execution of
~/.bashrc and ~/.ssh/rc on the remote side. Isn't this odd?

Greets,

--Walter

On 04/20/2011 05:25 PM, Males, Jess wrote:
> If you only ever want the user account to perform the one function, override their system shell.
>
> example:
> oper:x:519:519::/home/oper:/usr/local/bin/oper-only-ever-gets-to-do-this
.sh
>
> Regardless of how the account logs in, telnet, ssh, &c they'll only execute that one thing.
>
>
>
> ________________________________________
> From: listbounce (at) securityfocus (dot) com [email concealed] [listbounce (at) securityfocus (dot) com [email concealed]] On Behalf Of Walter de Jong [walter (at) sara (dot) nl [email concealed]]
> Sent: Tuesday, April 19, 2011 8:23 AM
> To: secureshell (at) securityfocus (dot) com [email concealed]
> Subject: ForceCommand executes shell
>
> Hi,
>
> I have set up a sshd_config that uses an alternate port number and
> ForceCommand to force the execution of a home-made service to our users.
>
> ForceCommand executes the command using 'shell' '-c', and as a result
> the user's .bashrc, .tcshrc, .whateverrc is being loaded -- which is
> something I was trying to prevent, because I'm trying to "force a
> command" upon them. In my case loading a .bashrc can be considered as a
> security hole.
>
> Is there any way around this? Maybe a different kind of setup would be
> better?
> I like using ssh for the service because of its excellent authentication
> mechanisms.
>
> I even made a patch to sshd session.c (see below) but I'd rather not
> have to maintain local mods to the source.
>
>
> Greets,
>
> --Walter
>
>
> void do_child()
>
> /*
> argv[0] = (char *) shell0;
> argv[1] = "-c";
> argv[2] = (char *) command;
> argv[3] = NULL;
> */
> argv[0] = "/bin/bash";
> argv[1] = "--norc";
> argv[2] = "--noprofile";
> argv[3] = "-c";
> argv[4] = (char *)command;
> argv[5] = NULL;
>
> execve(shell, argv, env);
> perror(shell);
> exit(1);
>
>
> --
> *** If you build it, they will come ***
>
> HPC Systems Programmer at SARA Computing and Network Services
> People should be able to e-mail me, spambots should not.

--
*** If you build it, they will come ***

HPC Systems Programmer at SARA Computing and Network Services
People should be able to e-mail me, spambots should not.

[ reply ]


 

Privacy Statement
Copyright 2010, SecurityFocus