Re: How Can I Securely Execute Script on Remote Windows Host?
- From: melsonr@xxxxxxxxxxxxxxxxxxx (Robert Melson)
- Date: Sat, 15 Sep 2007 05:00:09 -0000
In article <wvCdnfMHscInlHfbnZ2dnUVZ_sOrnZ2d@xxxxxxxxxxxx>,
"Will" <westes-usc@xxxxxxxxxxxxxx> writes:
What are the most secure options to allow a command line script written onI'd suggest two things: (1) that you recheck the authentication
machine A to synchronously execute another command line script written on
machine B, wait on response, and retrieve return code at the end of
execution. Assume client is UNIX and server is Windows.
I need some basic encryption around the initial authentication of the client
user to the server, but could live without encryption for the rest of the
connection. Some authentication of the machines involved in the
conversation independent of user authentication (similar to SSH) would be
nice. Some ability to limit the programs that can be executed on the
target to a group of programs that have been registered in advance would be
nice.
Microsoft does have solutions like WShell and WMT, but they are based on
port 135 and DCOM. We aren't willing to open up those ports through the
firewall because too many other services get exposed on the target system
with those ports available.
There are plenty of REXEC daemons for Windows, but these appear to be
trivially written and offer no encryption to protect password traversal over
the TCP connection, no machine authentication, and do nothing to stop
execution of any arbitrary EXE on the target computer.
SSH implementations certainly cover the authentication requirements, but I
don't find a straightforward way to do a synchronous execution of a remote
EXE through the SSH pipe. I do not want to login to a remote shell and do
things manually there. I want to launch an EXE from within a client-side
script and get a return code from one command in the script that will tell
me how the program ran on the remote host after it has finished running.
What options do I have?
options under SSH - there is an option available for, ahh,
"machine authentication"; (2) check out vpn, which tunnels a
secure virtual network between 2 or more machines over an
insecure medium.
Of the two options, SSH is probably the easier, vpn the more
"elegant" solution.
HTH,
Bob Melson
--
Robert G. Melson | Rio Grande MicroSolutions | El Paso, Texas
-----
"People unfit for freedom---who cannot do much with it---are
hungry for power." ---Eric Hoffer
.
- Follow-Ups:
- References:
- Prev by Date: Re: How Can I Securely Execute Script on Remote Windows Host?
- Next by Date: Hot Jobs - HCL - Noida/Chennai/Gurgaon/Mumbai
- Previous by thread: Re: How Can I Securely Execute Script on Remote Windows Host?
- Next by thread: Re: How Can I Securely Execute Script on Remote Windows Host?
- Index(es):
Relevant Pages
|