Secure Shell
Fixing $PATH programmatically for non-interactive SSH Mar 26 2010 03:01PM
Rémi PALANCHER (remi palancher inria fr) (2 replies)
Hi there,

I'm looking for a way to fix programmatically the $PATH after an
incoming SSH connection, not only for remote interactive shells, but
for remote command execution also.

I'm using Debian Lenny with , and currently I have :

user@host:~$ ssh -V
OpenSSH_5.1p1 Debian-5, OpenSSL 0.9.8g 19 Oct 2007
user@host:~$ ssh localhost
[...]
user@host:~$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/games:/myowndir
user@host:~$ exit
user@host:~$ ssh localhost 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

I would like to add /myowndir to the $PATH for remote command
execution, as well as for remote login shells.

As far I've investigated, $PATH is fixed by /etc/profile for interactive
connection. But unfortunately, for remote command execution, this script
is not executed.

I would like to add this dir to $PATH for all users except the famous
one with uid 0. So, I guess I can't use those basics key/value files
such as /etc/environment or ~/.ssh/environment.

Is there any simple way to deal with such constraints in OpenSSH?
Intuitively, I was thinking of well-thought combination of 'UsePAM yes'
and modules in /etc/pam.d/sshd?

Thanks in advance for any kind of help,
--
Rémi PALANCHER IJD/SMI
Systems and networks administrator on Grid'5000
INRIA Saclay Building H
tel: +33 1 74 85 42 45 Office 015

[ reply ]
Re: Fixing $PATH programmatically for non-interactive SSH Mar 26 2010 04:22PM
Charles Bradshaw (brad bradcan homelinux com)
Re: Fixing $PATH programmatically for non-interactive SSH Mar 26 2010 04:18PM
Greg Wooledge (wooledg eeg ccf org)


 

Privacy Statement
Copyright 2010, SecurityFocus