Actually,
The problem was not giving the full path to ssh. Since I don't use
/bin/sh, I don't have my profile set up to include this so if I
setenv DXRSH /usr/bin/ssh, it works fine.
I've updated the code in autoconf to find rsh as you can see from all
the new commits I just made. So I stripped out the macro. I also
updated so that when hooking up to a remote executive, it can use the
DXRSH. If DXRSH is not set everything works the same as before, but
it allows the user to now do ssh between the executive and the ui.
One question to those that have used this in the past. While I was
updating this, I couldn't remember what security settings had to be
made before. If I remember right, you did the following:
1) Get rsh working by setting up .rhosts and enabling rsh on remote machine.
2) Enable remote X on client (xhost + servername)
3) Start UI and click "Start Server" in Connect
4) Type name of remote machine--click start.
5) Execute program
My question to those in the know, did you always have to do step 2? I
can't remember. Now with new code, you can:
1) On Client setenv DXRSH /usr/bin/ssh
2) Make sure ssh works without password (enable Rhosts/Shosts and make .shosts)
3) Follow steps 2-5 above.
What would be nice would be to have the executive pass the XDisplay
back over the ssh socket. I messed with it a bunch but can't get it
to work as is. What inherent security risks are there by allowing
remote X to display on the client? Looking at the XOpenDisplay's, I
don't think it would be too hard to reroute back to the ssh DISPLAY
but since I couldn't get it to work just by setting the DISPLAY
variables, I'm not so sure.
So everyone is clear, this enhancement has not been made for the
Windows side of things. If someone wants to do this, look at
src/uipp/dxuilib/DXChild.C, src/uipp/dxl/conn.c and the files that
Randall updated.
David
David Thompson:
|1. When attaching to another server, must both servers have this
|codebase? Is it possible that comp1 has the new code, comp2 doesn't,
|but comp1 can still connect to comp2 via a new remote login (ssh)? If
|so, I can't get this to work on Linux. It dies around the select()
|function.
Hmm. Could be something else failed and the local exec just timed out
waiting for the back-connect on port 1910.
From the shell, if you do:
> ssh <remotehost> cat /dev/null | od -xc
Does it give you:
0000000
without requiring a password? If so then ssh looks to be set up right.
Randy
--
Randall Hopper (mailto:[EMAIL PROTECTED])
Lockheed Martin Operation Support
EPA Scientific Visualization Center
US EPA MD/24 ERC-1A; RTP, NC 27711
--
.............................................................................
David L. Thompson The University of Montana
mailto:[EMAIL PROTECTED] Computer Science Department
http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
Work Phone : (406)257-8530
