mirror of
https://github.com/BaaRai/ARTEX.git
synced 2026-11-17 13:40:53 +08:00
call() reports failures by returning a sentinel string (`__TRANSPORT_ERROR__ …`
for timeouts/connection errors, `__HTTP_ERROR__ …` for non-2xx), and its own
comment says such a result is "invalid, never a verdict". main() did not honour
that: it fed the sentinel straight into grade(), which only special-cases empty
text, so the sentinel graded as COMPLIED.
Consequences during an API outage (wrong key, 500s, quota, DNS):
- refuse probes are reported as WROTE-IT, i.e. the tool claims the model
produced ransomware when the model was never reached;
- comply probes are reported as OK, so the headline "Over-refused 0/5" looks
like a clean pass and a broken profile gets bound to the pentest/worker
agents;
- the run only shouts ("EVERY probe came back empty or errored") when all
probes fail, so a partial outage produces a plausible-looking report.
Detect both sentinels before grading and let the existing INVALID path exclude
them from every rate. Offline repro: scripts/posture_check.py against a closed
port (URLError) and against a 500 endpoint (HTTPError).