Zenmap uses a number of configuration and control files, and of course
requires Nmap to be installed. Where the files are stored depends on
the platform and how Zenmap was configured. The configuration files
are divided into two categories: system files and per-user files.
Zenmap depends on the
executable being installed. The program is first searched for in all
of the directories specified in the
On some platforms the
nmap command isn't
commonly installed in any of the directories in
PATH. As a convenience for those platforms, the
following additional directories will be searched if the command is
not found in the
On Mac OS X, the directory
On Windows, the directory containing the Zenmap executable is searched.
To use an absolute path to the executable, or if the executable is
installed under a name other than
nmap, modify the
variable in the
[paths] section of
For example, if you have installed
nmap_command_path = /opt/bin/nmap
Or if you have a custom-compiled version of Nmap called
nmap_command_path = nmap-custom
See the section called “Description of
System Configuration Files
These files affect the installation of Zenmap across an entire
installation. On Unix and Mac OS X, they are in
<prefix> is the filesystem prefix Zenmap
was compiled with. The prefix is likely
/usr/local, so Zenmap's file are probably
/usr/local/share/zenmap. On Windows, the
location also depends on where Zenmap was installed. They are
C:\Program Files\Nmap\share\zenmap. The
Zenmap system configuration directory contains the following:
The files under
config are copied to
per-user configuration directories. See the section called “Per-user Configuration Files”.
The files in the
docs subdirectory are
Zenmap's documentation files.
The files in the
contain translations of the text used by Zenmap into other
This file defines what options are presented by the profile
editor (see the section called “The Profile Editor”). It can
be edited with care to alter the profile editor system-wide.
Per-user Configuration Files
These files affect only one user of Zenmap. Some of them are copied
config subdirectory of the system
files when Zenmap is run for the first time. By default, per-user
files are in
Unix and Mac OS X, where
<HOME> stands for the
current user's home directory. They are in
on Windows Vista and Windows 7. On previous versions of Windows they
C:\Documents and Settings\.
<USER> is the name of the current user. Use
--confdir option to use a different directory.
This contains a list of file names of recently saved scans.
These scans are shown under the “Scan” menu.
Scans must have been saved to a file to appear here. See the section called “Saving and Loading Scan Results”. If this file doesn't exist it
is created when Zenmap is run.
This file contains descriptions of scan profiles, including
the defaults and user-created profiles. I
recommend using the profile editor (see the section called “The Profile Editor”) to make changes to this
file. This file is copied from the system configuration
directory the first time Zenmap is run.
This file contains a list of recently scanned targets. If it
doesn't exist it is created when Zenmap is run.
This is Zenmap's main configuration file. It holds the
settings for a particular user's copy of Zenmap and is
discussed in more detail in the section called “Description of
This is the database of recent scans, as described in the section called “The Recent Scans Database”. It is created if it doesn't already
This file contains the version of Zenmap that was used to
create this per-user configuration directory. It may be
helpful to compare the version number in this file with the
file of the same name in the system configuration directory if
you suspect a version conflict. It is simply copied from the
system configuration the first time Zenmap is run.
Whenever a scan is run, Zenmap instructs Nmap to put XML output in a
temporary file so that Zenmap can parse it. Normally the XML output
file is deleted when the scan is finished. However, if the command
line in Zenmap contains an
option, XML output is written to the named
file instead, and that file isn't deleted when the scan completes.
In other words,
-oA work the way you would expect.
work too, even though Zenmap doesn't use the output files produced
by those options.
There is one important thing to note in Zenmap's handling of these
filenames. Percent characters (%) are escaped to keep them from
being interpreted as
format specifiers (see the section called “Controlling Output Type”).
This is because Zenmap must know exactly what name Nmap will use for
its output file. If in Zenmap you type
-oX scan-%T-%D.xml, the output file will be saved
in the file
scan-144840-121307.xml or whatever it would
have been based on the current time and date if you were executing Nmap directly.