v1.29.2 — Console port scans, CLI fixes and corrected docs

Port scans started from the web console now work. Upgrade if you use the console.

pip install --upgrade phantomsignal

Important

Console scans that include port_scan now send real probes to the target directly from your IP. Before this release they found no open ports, so a console scan showing none wasn't a clean result, and you may want to rerun it. The report marks the module as attributable, and Tor and Covert scans still skip it.

Fixed

• Console port scans. The form sent a profile name like common where the scanner expected a list of ports. The Common, Top 1000 and Full range options now take effect, and port_scan_fast handles them too.
• --modules rejects unknown names. The documented --modules dns,port,tech ran nothing and still reported a completed scan. Unknown names are now an error, and you can separate names with commas or repeat the flag.
• --format xlsx works on the CLI, for both scan and export.
• phantomsignal init points at Integrations for API keys.
• The console's profile cards say what profiles do. They promised modules, port ranges and durations that profiles don't control.

Documentation

• The usage guide lists every command and scan flag, with correct defaults.
• Scan profiles are described as they work: Deep currently runs the same modules and ports as Standard.
• Troubleshooting has the correct database path, log location and Docker volume name.

Testing

Checked with packet captures of scans using the form's options, including the Tor toggle and Covert profile. The Full range option wasn't run, and neither was real Tor with those options.

Full details: changelog