rsh/ssh problem

rsh/ssh problem

Post by Norman Teferl » Sat, 25 Jan 2003 21:27:36



Dear all,

I am running Mdk 9.0 with service sshd.
A program requires that it can carry out remote shell commands in its
own
user environment, eg:
rlogin -l user host (with host being the host name of the localhost)
I have set up the .rhosts file so it contains
host.domain user
in order for user to do a rlogin or rsh.
However, I get a connection refused.

Can anyone help, please ?
Thanks.

Norman

 
 
 

rsh/ssh problem

Post by Pat » Mon, 27 Jan 2003 07:38:37


Greets,


> Dear all,

> I am running Mdk 9.0 with service sshd.
> A program requires that it can carry out remote shell commands in its
> own user environment, eg:
> rlogin -l user host (with host being the host name of the localhost)

The sshd server will allow secure *SSH* connections, by default on port 22.  When you use rlogin you
are using a different protocol, connecting to a different port (513, I think).  These are not the
same.

I wouldn't recommend using the r(sh|login|.*), you can run commands on the remote host using ssh:


If you need to automate the process and do not want to be asked for a password when executing the
remote command, you can generate an authentication key pair to allow passwordless access (this
obviously has some security implications as access will be granted to anyone who manages to get
their hands on the ssh identity file, so be careful), see the ssh-keygen man page for details.

HTH.
--
Pat Deegan,
Registered Linux User #128131
http://www.psychogenic.com/contact.en.html

 
 
 

rsh/ssh problem

Post by Bill Unr » Mon, 27 Jan 2003 09:12:27


]Greets,

]> Dear all,
]>
]> I am running Mdk 9.0 with service sshd.
]> A program requires that it can carry out remote shell commands in its
]> own user environment, eg:
]> rlogin -l user host (with host being the host name of the localhost)

]The sshd server will allow secure *SSH* connections, by default on port 22.  When you use rlogin you
]are using a different protocol, connecting to a different port (513, I think).  These are not the
]same.

]I wouldn't recommend using the r(sh|login|.*), you can run commands on the remote host using ssh:


]If you need to automate the process and do not want to be asked for a password when executing the
]remote command, you can generate an authentication key pair to allow passwordless access (this
]obviously has some security implications as access will be granted to anyone who manages to get
]their hands on the ssh identity file, so be careful), see the ssh-keygen man page for details.
To add to this you could write a script called rlogin, which takes the
command options and creates an ssh connection. So this only if the
program refuses to use anything but rlogin.

 
 
 

1. rsh/ssh problems under Solaris 2.5

: Mike, Im not sure I am following you here. It seems from your post you
: might not be aware of how rsh works. The manual page for rsh specifically
: defines the access you need via /etc/hosts.equiv or ~/.rhosts with the
: hostname in /etc/hosts. example ~/.rhosts "machine1 username" which is
: working fine in our environment with 2.3-2.5.1 and IRIX 5.3. Did you originally
: configure your set up? Could you provide some more information?

Drew, thanks for the input.  However, I *had* rsh working *fine* under
Solaris 2.3....when I upgraded to 2.5, rsh broke, and I can't fix it.......
I don't want to go back to 2.3 *just* to backup the Linux boxes.  
Yes, I did the original setup, and it worked like a champ.....it
was a great tool for backing up the 3-4 Linux boxes that we have
without buying a tape drive for each machine.

Again, thanks for the input, and sorry about not putting all of the
facts in the post.....

mike

--
Mike Weber,  Computer Sciences Corp., ERIC Facility

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"As your attorney, it is my duty to inform you that it is not important
that you understand what I'm doing, or why you're paying me so much money.
What's important is that you continue to do so."
-Hunter S. Thompson's attorney

2. FreeBSD and CHAP scripting with ATT

3. rsh + ssh = problem

4. Origin of the name "UFS" for FFS?

5. rsh/ssh problem

6. Guessing type of File

7. Ssh/Rsh problems

8. statvfs has bitten me

9. TCP Wrapper / rsh problem (rsh hangs)

10. can ssh-agent work between ssh-2.3 and ssh-3.5

11. Setting $TERM when using rsh and ssh with bash

12. ssh/rsh

13. rsh, telnet, ssh hangs my terminal window...