NmapWorker / News: Recent posts

NmapWorker now uses log4php for logging.
Also lots of debug and trace messages are added so it is possible to get much more informations about NmapWorker's work.

NmapWorker polls a jobDirectory, executes nmap and exports the results into a database.

NmapWorker searches a specified directory (see: nmapworker.ini) for .job files. It it finds any that match the
correct format (see: job_example.job) it creates jobs from it and executes nmap with the appropriate command line
parameters. The result is read and parsed and then passed to an exporter that stores the result in a database.
The default behavior is that NmapWorker immediately deletes the .job files it reads, so they are not to be processed
again. If deleting fails the job will not be processed. This way it is possible to run multiple instances of
NmapWorker that synchronize via the .job files.
This way another application can control NmapWorker and start scans by copying .job files into the jobDirectory;
however, it is possible to change NmapWorker's behavior to not delete the files, so you may set up static and
periodic scans.... read more