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: Environment Settings

Subject: RE: Environment Settings
Date: Mon, 9 Jul 2007 13:48:31 -0600
I am using normal Unix shell (ksh).
 
I use ssh to submit application job. And I hope the ssh command can keep
as simple as to have no 'presetting command' such like execute the
dotfiles. In other words, I hope to see the 'environment variables' if I
type the following command line:

ssh host1 set 

Above command assumes that I am accepted by host1 through key
authentication. As I tried, the above command does not read the dotfiles
...

Jialing Liang
jialing.liang@cmgl.ca

-----Original Message-----
From: listbounce@securityfocus.com [mailto:listbounce@securityfocus.com]
On Behalf Of Greg Wooledge
Sent: Monday, July 09, 2007 6:03 AM
To: Jialing Liang
Cc: secureshell@securityfocus.com
Subject: Re: Environment Settings

On Thu, Jul 05, 2007 at 01:27:25PM -0600, Jialing Liang wrote:
ssh user can have an 'environment' file under $HOME/.ssh on ssh
server.
That is good enough. However, in case that the $HOME is a shared 
directory among several ssh servers, how to make different
environment 
settings for each of these servers?

You could run various commands from the user's shell-specific dotfiles
(e.g. ~/.bash_profile or >~/.login).  For example, in bash syntax:

 case $(uname -n) in
   host1) export FOO=bar1;;
   host2) export FOO=bar2;;
   ...
 esac

A lot depends on what you're doing with ssh.  If you're not using a
traditional Unix shell, then I don't have an answer for you.

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