I got to thinking, doesn't ssh handle things like "[EMAIL PROTECTED]"
directly? So is it necessary to enhance the UI to need the username?
David
David Thompson:
|Actually, for point 2, the code I'm talking about can't be fixed as
|easily as just changing the shell, if we want to provide the ability
|to use something like ssh [EMAIL PROTECTED], can it? Don't we need
|to add some of the code that you did for the dxexec stuff with the
|username?
For those places that are assuming the remote user is the same as the local
user, yes you're right. Execution groups was one of these spots.
A quick grep of the source files for "rsh" reveals that (except for the two
MSWin #ifdef sections) all of those spots know how to provide a username.
So the issue is the clients of those low-level routines (DXLStartDX,
DXApplication::startServer, etc.) that aren't obtaining and providing a
username (allowing the low-level rsh routines to default to the local
username).
I'm not sure how many places these username references surface in dxui or
the APIs. A few places are certainly Connection->Start Server... and
DXLStartDX. Guess we'd need a username blank for the former, or have it
take the "hostname" of [EMAIL PROTECTED] like my execution group patch. The
former
might be better because it's more intuitive from the usability standpointa,
but I didn't want to get into GUI reorg issues while testing the patch. ;-)
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
