The idea here is that he'd like to run commands on a remote windows box, from the nix box. Psexec allows you to run commands on remote win boxes, however there exists only a Win32 version.
SSH is fine and good, but Psexec requires nothing more than a fresh windows install, so there'd be no need to deploy new services like ssh. Having administered a large windows domain, I can wholeheartedly agree that psexec is a time saver. -Lee -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Exibar Sent: Thursday, May 06, 2004 3:50 PM To: [EMAIL PROTECTED] Subject: RE: [inbox] RE: [Full-Disclosure] Psexec on *NIX At first I thought this request was coming from just someone who doesn't know about SSH, the 'r' services, etc. No-one knows everything and that's cool, but then I thought about it for a second...and now to me this sounds either like someone who wants to ILLEGALLY use other resources on some elses network, wants to write a worm that will access anything he wishes on any network he wishes, or he's simply trolling because he's bored. ahhh, I know, a high school kid who wants to change his grades or impress a freshman or some chick to get laid...well, I've done some funky things to get laid, so I'll give him that one :-) I don't know any UNIX admin that would have a problem using SSH or rshell, etc. Exibar > -----Original Message----- > From: Chris Carlson [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 06, 2004 4:19 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [inbox] RE: [Full-Disclosure] Psexec on *NIX > > > 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 > > _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
