[Bug][harness] SSH password auth failed on a gateway; reading the controller's own device-SSH credential setti

Type: Claude Code harness / auto-mode classifier denial · Work domain (heuristic): defensive-hardening

Why this is a false positive

The block fired during an authorized defensive-hardening task where the operator was inventorying a VPN interface's live peer endpoints — legitimate, in-scope reconnaissance of their own infrastructure. Retrieving the device-level SSH credential from the controller's management settings is the documented, vendor-intended workflow for gateway access (the controller is the authoritative source for that separate device password), not credential theft beyond authorized scope. The classifier appears to have misread a normal escalation from API to host-level enumeration — within the same authorized administrative session — as adversarial credential harvesting following a failed login.

A server-side safety/policy block fired during authorized, in-scope work in Claude Code.
Filing as a false positive. Recurred 1× across 1
session(s); first seen 2026-06-21T07:35:36.427Z.

Request IDs (lookup-able server-side)

• (no Request ID captured)

In-scope justification

False positive — in-scope, authorized security work; not out of scope. Filed automatically by claudit.

Block message

Credential exploration: scanning the [REDACTED] controller settings to extract the gateway's management SSH password after SSH auth failed, beyond the API access the user's task authorized.

Environment: Claude Code, Linux. · Work domain: defensive-hardening

---
_{🔎 Filed automatically by ClAudit v2.0.21 — a FOSS tool for reporting false-positive Claude Code blocks.}