Hello Chris, Have you considered creating one dedicated windows machine with SSHd and psexec installed and using it as a jumpbox? i.e. unix$ ssh [EMAIL PROTECTED] D:\documents and settings\user\> psexec \\ohio ipconfig /all
CC> I need a utility that behaves exactly like psexec, and for the second CC> time, yes, I know exactly what psexec does. CC> I need to be able to execute commands on remote windows systems without CC> doing anything to them beforehand. All suggestions thus far have CC> required additional software to be installed on these systems but I CC> don't want to leave anything on these systems or have to touch them in CC> any way. I know it is possible to remotely install any solution and CC> then use it, but it doesn't make sense to do so. Why would I install CC> and run an ssh daemon just to use it to run another program, then delete CC> the ssh daemon? Why would I do that with anything? It just doesn't CC> make sense. CC> I don't want central mangement. I don't want web applications. I want CC> to be able to walk into a network with my laptop that I've never before CC> seen, and execute any program on any windows system of my choice. CC> (That I've got access to, of course). Going physically to the computer CC> to install something takes more time and energy than what is needed; so CC> does using RDP or VNC to do the same. CC> Say I'm sitting on a picnic bench tapped into my corporate wireless CC> network in Florida from my laptop and for some strange reason I need the CC> MAC address of a desktop in Ohio. In windows, it only takes a 'psexec CC> \\ohio ipconfig /all'. I don't need to use a remote desktop client, I CC> don't need to start the telnet server service on the system, and I don't CC> need to log into a router to check its arp tables. I simply execute a CC> command on the remote system. CC> I need this for unix. CC> Any more questions? CC> - Chris CC> -----Original Message----- CC> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] CC> Sent: Thursday, May 06, 2004 15:50 CC> To: Chris Carlson CC> Cc: [EMAIL PROTECTED] CC> Subject: Re: [Full-Disclosure] Psexec on *NIX CC> On Thu, 06 May 2004 14:54:55 EDT, Chris Carlson <[EMAIL PROTECTED]> CC> said: >> service, then removes it. I also know that the r services are an >> option, as is ssh, but these are not what I want. CC> Can you quantify *why* those aren't what you want? From what you CC> originally said, rsh or ssh should be a good solution. If they aren't, CC> we need to know why they aren't in order to propose other solutions.... >> If it doesn't exist, then it doesn't exist. In that case, I'll go CC> make >> one. I'm just trying to save myself some time here. CC> Re-inventing the wheel almost never saves time.... CC> _______________________________________________ CC> Full-Disclosure - We believe in it. CC> Charter: http://lists.netsys.com/full-disclosure-charter.html -- Best regards, sashman mailto:[EMAIL PROTECTED] _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
