I would tend to agree, but this is not for the unwashed masses - I really
don't have any. This is just for the linux box under my desk to go
interrogate our websphere servers and report back to me what they are
doing. Nothing terribly fancy. Actually it's gonna be quite ugly since I'm
writing it in either shell script or rexx.
"Kielek, Samuel"
<[EMAIL PROTECTED]
rriott.com> To
Sent by: Linux on [email protected]
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: Using ssh to execute a command
on another system
02/08/2005 10:18
AM
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
If you implement kerberos, you could continue to use rexec, rsh, rcp,
telnet, ftp, etc. and it would be secure since the kerberized versions
encrypt the traffic. This is sometimes easier to implement and control
than a ssh approach as it is familiar to the users since they get to
continue doing things essentially as they always have.
Sam Kielek
Marriott International
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Alan Altmark
Sent: Tuesday, February 08, 2005 11:07 AM
To: [email protected]
Subject: Re: Using ssh to execute a command on another system
On Tuesday, 02/08/2005 at 09:38 CST, James Melin
<[EMAIL PROTECTED]> wrote:
> Got a question about ssh....
>
> rexec provides an ability to execute a command on a remote system and
pass
> the ID/Password on the command line. This prevents the session from
> prompting for a password.
>
> e.g: rexec -l username -p password hostname command
>
> the problem with rexec , of course, is that it is unsecure.
It is unsecure if it flows over the open network. If it remains on a
virtual network connection, it remains secure.
> What I am looking to do is to ssh to a specific linux, execute a
command,
> capture the output of that command, parse that output and set some
> variables and write out a 'status page' html file. I do not know how
to
> handle being asked for a password in a shell script.
A remote system could enter a VM system with https, authenticate at that
level, and then request REXECs.
Just pointing out that there are multiple ways to solve the problem. (I
happen to like SSH, but there are other solutions, too.)
Alan Altmark
z/VM Development
IBM Endicott
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
