vulnersCom/nmap-vulners v2.0.1

nmap-vulners 2.0.1

on GitHub

A housekeeping release. Nothing about scanning changed - the same
identities are found, the same lookups are made, the same report is printed.
If 2.0 works for you, there is nothing here you need.

What changed is that the tree now meets
Nmap's own Code Standards, which
HACKING names as the authority for a script that wants to live in nmap's
tree, and a gate keeps it that way.

• tools/nmap_style.py is that standards page expressed as a test, and it
  runs in CI as the eighth gate: no tabs, no trailing whitespace, LF endings,
  UTF-8, one newline at end of file, lines under 80 columns, no semicolons, no
  bin/bit, explicit endianness in string.pack, structured output, the
  four fields a script must declare, --; for private NSEdoc, and PEP 8 for
  the Python. Fourteen deliberate violations were planted to prove it catches
  them.
• 1 025 lines were rewrapped to 79 columns across the script, the test
  suites, the tools and both installers.
• Private NSEdoc opens with --;, as the standards ask. vulners.nse
  keeps two --- blocks, and they are the two that should be there: the
  NSEdoc header, and the one introducing portrule.
• Three kinds of line are deliberately left long, and the gate says why: a
  line inside a Lua [[ long bracket ]], a line inside an @output or
  @xmloutput block, and LICENSE. Each is a verbatim capture, and
  rewrapping one would make it a sample of something that never happened.

The end-to-end gate's keyless checks were not keyless on a machine with a key
stored at ~/.nmap/vulners.key. Pinning HOME does not isolate the lookup:
nmap resolves ~/.nmap through getpwuid(getuid()), so the developer's own
key was picked up and every "keyless" check quietly ran the keyed path. The
suite now pins NMAPDIR at a scratch directory holding an empty
vulners.key, and a new check proves both halves of that - that the pin is in
place, and that a key in NMAPDIR is what a scan uses.

curl -fsSL https://raw.githubusercontent.com/vulnersCom/nmap-vulners/master/install.sh | sh

PowerShell, as Administrator:

irm https://raw.githubusercontent.com/vulnersCom/nmap-vulners/master/install.ps1 | iex

The script's api_version stays 2.0: it names the request generation the
service sees, not the release, and no request changed shape.

Full Changelog: v2.0...v2.0.1