full-disclosure - Psexec on *NIX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

From: Ian.Latter at mq.edu.au (Ian Latter)
Subject: Psexec on *NIX

I shouldn't have replied so hastily, Ken and Kathy reckon you're
screwed;

  http://www.kenandkathy.net/kkexec/index.shtm


the RPC 'sploits last year had the psexec loop hole closed (?).  Might
be worth talk to them about getting their kkexec compiled up for Linux,
they seem conducive to US greenback.



----- Original Message -----
>From: "Chris Carlson" <chris@...pucounts.com>
>To: <Valdis.Kletnieks@...edu>
>Subject:  RE: [Full-Disclosure] Psexec on *NIX
>Date: Thu, 06 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@...edu [mailto:Valdis.Kletnieks@...edu] 
> Sent: Thursday, May 06, 2004 15:50
> To: Chris Carlson
> Cc: full-disclosure@...ts.netsys.com
> Subject: Re: [Full-Disclosure] Psexec on *NIX 
> 
> On Thu, 06 May 2004 14:54:55 EDT, Chris Carlson <chris@...pucounts.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
> 

--
Ian Latter
Internet and Networking Security Officer
Macquarie University