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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: swmike at swm.pp.se (Mikael Abrahamsson)
Subject: Psexec on *NIX 

On Thu, 6 May 2004, Chris Carlson wrote:

> 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

What unix comes without any kind of remote login service such as sshd, 
rexec, telnetd or alike?

Is the thing you're looking for the security model that windows has, in
that you can authenticate to any machine running on same domain and that's
how it knows if you're allowed to execute commands?

There is no such thing default in *NIX. You're probably looking for 
something like Kerberos (which is what Microsoft used as far as I know) 
but it doesnt come standard with most unixes.

According to <http://www.sysinternals.com/ntw2k/freeware/psexec.shtml> 
psexec is a "lightweight telnet replacement", so I don't understand what 
it does that ssh/telnet doesnt do for you?

You can use "ssh <host> -l <username> ifconfig" to run "ifconfig"  
directly on a remote computer without having to actually login and get a
prompt on that machine, if that's what you were looking for.

-- 
Mikael Abrahamsson    email: swmike@....pp.se