Being a graphical application, most of Zenmap's functionality is
exposed through its graphical interface. Zenmap's command-line
options are given here for completeness and because they are sometimes
useful. In particular, it's good to know that the command
zenmap <results file>
starts Zenmap with the results in <results
file> already open.
zenmap [
<options>
] [
<results file>
]
-f, --file <results file>Open the given results file for viewing. The results file may be
an Nmap XML output file (.xml, as produced by
nmap -oX), or a file previously saved by
Zenmap. -h, --helpShow a help message and exit. --confdir <dir>Use <dir> as the per-user
configuration directory. -n, --nmap <Nmap command line>Run the given Nmap command within the Zenmap interface. After
-n or --nmap, every remaining
command line argument is read as the command line to execute. This
means that -n or --nmap must be
given last, after any other options. Note that the command line must
include the nmap executable name: zenmap
-n nmap -sS target. -p, --profile <profile>Start with the given profile selected. The profile name is just
a string: "Regular scan". If combined with
-t, begin a scan with the given profile against the
specified target. -t, --target <target>Start with the given target. If combined with
-p, begin a scan with the given profile against the
specified target. -v, --verboseIncrease verbosity (of Zenmap, not Nmap). This option may be
given multiple times for even more verbosity printed to the console window used to start Zenmap.
If Zenmap happens to crash, it normally helps you send a bug report with a
stack trace. Set the environment variable
ZENMAP_DEVELOPMENT
(the value doesn't matter) to disable automatic crash reporting and have
errors printed to the console. Try the Bash shell command
ZENMAP_DEVELOPMENT=1 zenmap -v -v -v to get a
useful debugging output.
On Windows, standard error is redirected to the file
zenmap.exe.log in the same directory as
zenmap.exe rather than being printed to the
console.
|
|
