cxg changelog
Version 1.9.1
Upgrading
After upgrading an existing installation, run cxg pentest install --force. The fix
below is in the embedded Python pentest pipeline, and replacing the binary alone does not
replace the files under ~/.cert-x-gen/pentest/.
Fixed
cxg.oracle.excludedRecordsverdicts bind when the scope has a path. With a landing scope such as--scope http://host/dashboard, the oracle measured/api/xat the service origin while the finding claimed/dashboard/api/x, so a correct row-filtering fix came backinconclusive_refusal(unverified) instead of refuted (proven), and a leak was not confirmed by the oracle. The claim is now resolved at the service origin, the way the oracle’s requests are, through bothcxg scanandcxg pentest run. The other class oracles build their requests from the full--target, so their claims already bound and are unchanged.cxg pentest run --helpdescribed 1.8.0 session behaviour. It said a dead session only warns without--ciand that--skip-health-checkforce-marks profiles alive. Since 1.9.0 an expired profile exits 5 with or without either flag, and probes for ready services still run. The--ci,--skip-health-checkand exit-code 5 help now say so, and--cireads as what it still does: refuse a world-accessible--auth-dir.

