Full Disclosure mailing list archives
RE: Psexec on *NIX
From: "Chris Carlson" <chris () compucounts com>
Date: Thu, 6 May 2004 16:19:17 -0400
I need a utility that behaves exactly like psexec, and for the second time, yes, I know exactly what psexec does. I need to be able to execute commands on remote windows systems without doing anything to them beforehand. All suggestions thus far have required additional software to be installed on these systems but I don't want to leave anything on these systems or have to touch them in any way. I know it is possible to remotely install any solution and then use it, but it doesn't make sense to do so. Why would I install and run an ssh daemon just to use it to run another program, then delete the ssh daemon? Why would I do that with anything? It just doesn't make sense. I don't want central mangement. I don't want web applications. I want to be able to walk into a network with my laptop that I've never before seen, and execute any program on any windows system of my choice. (That I've got access to, of course). Going physically to the computer to install something takes more time and energy than what is needed; so does using RDP or VNC to do the same. Say I'm sitting on a picnic bench tapped into my corporate wireless network in Florida from my laptop and for some strange reason I need the MAC address of a desktop in Ohio. In windows, it only takes a 'psexec \\ohio ipconfig /all'. I don't need to use a remote desktop client, I don't need to start the telnet server service on the system, and I don't need to log into a router to check its arp tables. I simply execute a command on the remote system. I need this for unix. Any more questions? - Chris -----Original Message----- From: Valdis.Kletnieks () vt edu [mailto:Valdis.Kletnieks () vt edu] Sent: Thursday, May 06, 2004 15:50 To: Chris Carlson Cc: full-disclosure () lists netsys com Subject: Re: [Full-disclosure] Psexec on *NIX On Thu, 06 May 2004 14:54:55 EDT, Chris Carlson <chris () compucounts com> 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.
Can you quantify *why* those aren't what you want? From what you originally said, rsh or ssh should be a good solution. If they aren't, 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
make
one. I'm just trying to save myself some time here.
Re-inventing the wheel almost never saves time.... _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Current thread:
- Re: Psexec on *NIX, (continued)
- Re: Psexec on *NIX François Harvey (May 07)
- RE: Psexec on *NIX Chris Carlson (May 06)
- Re: Psexec on *NIX Valdis . Kletnieks (May 06)
- RE: Psexec on *NIX Bill Royds (May 06)
- Re: Psexec on *NIX whiplash (May 06)
- Re: [despammed] Re: Psexec on *NIX whiplash (May 06)
- Re: Psexec on *NIX Ondrej Krajicek (May 06)
- Re: Psexec on *NIX Valdis . Kletnieks (May 06)
- Re: Psexec on *NIX hybriz (May 06)
- Re: Psexec on *NIX Ondrej Krajicek (May 07)
- Re: Psexec on *NIX Nico Golde (May 07)
- RE: Psexec on *NIX Chris Carlson (May 06)
- RE: Psexec on *NIX Scott Taylor (May 06)
- Re: Psexec on *NIX Jon S. (May 06)
- Re: Psexec on *NIX Ondrej Krajicek (May 07)
- RE: Psexec on *NIX Michael Gargiullo (May 06)
- RE: Psexec on *NIX Mikael Abrahamsson (May 06)
- RE: Psexec on *NIX xtrecate (May 08)
- RE: Psexec on *NIX Ron DuFresne (May 10)
- RE: Psexec on *NIX Frank Knobbe (May 06)
- RE: Psexec on *NIX Pavel Kankovsky (May 06)
- RE: Psexec on *NIX Paul Schmehl (May 06)
(Thread continues...)