1
0
mirror of https://github.com/nmap/nmap.git synced 2025-12-09 14:11:29 +00:00
Files
nmap/nselib/data/psexec
ron 934cf2edf0 Significant changes, both bugfixes and best practice changes, to smb-psexec.nse. Primarily:
o It no longer uses the global environment to store the modules table
o It now uses loadfile() to load the configuration files, which follows best practices better
o The module() line at the top of the configuration files is no longer required, but if it exists all that happens is a warning is printed
o Worked around what appears to be a bug in one person's Nmap install where absolute paths didn't resolve properly -- I couldn't replicate, but he confirmed it was fixed
2010-08-07 19:36:47 +00:00
..

The files in this directory are the data files required for smb-psexec.nse. 

The .lua files are configurations. Each of these defines a profile for a 
psexec execution. 

nmap_service.exe is a program that facilitates the operation of smb-psexec.nse. 
It is uploaded to the remote host and runs the programs it's directed to run,
redirecting their output to a file. This file is then downloaded by the 
script and displayed to the user. 

When Nmap released version 5.20, it was discovered that some over-zealous
antivirus software tagged this program as spyware[1]. For that reason, when
stored on the host machine, it is now encoded by xoring every byte of the
file with 0xFF. When uploaded to a target machine, it is decoded in-stream. 
This prevents programs on the host machine from tagging it as malicious, but
does not prevent the target from detecting it (which is arguably a good thing). 

The encoder.c program reads a program from stdin, encodes it by xoring with
0xFF, and writes it to stdout. 

[1] http://seclists.org/nmap-dev/2010/q1/198