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]

'ssh' command behavior

Subject: 'ssh' command behavior
Date: Thu, 25 Nov 2004 18:04:11 +0100
Hi,

 I'm about to switch an application from using rsh to (Open) ssh and
bumped into a problem. My (web) application runs on Solaris and its
task is to run, control, and stop processes running on other Solaris
systems.

 If someone clicked on 'start' button, it started a local process,
which in turn started a process via rsh on the remote Solaris server.
It was like:

 rsh -l username servername '/tmp/startscript.sh'

These two processes ran until one of them died, i.e. any of these
process died, the other one died too. This way I could control exactly
whether a remote process still runs, and I also was able to stop this
exact process. In fact, rsh made the whole control of the remote
process transparent, I got the stdin, stdout, stderr of the process
locally, and even the signals sent to the local process were forwarder
exactly to the remote process.

Now, I thought I can just simply replace the rsh with ssh, I supposed
this mechanism works the same way. However, if I kill the local
process, the remote one doesn't end.

Could you please tell me, how this mechanism works on ssh?

Regards,

Zoltan



<Prev in Thread] Current Thread [Next in Thread>
  • 'ssh' command behavior, Sebestyén Zoltán <=