Patch Changes
-
#136
ceb1981Thanks @tufantunc! - Say what a decision was about, and what a refusal leaves you able to do.binarynow names the command the class describes (#134). Since elevation began to be detected per segment in 2.2.4, the class and the binary could describe different commands:echo hi; sudo idrecordedbinary: "echo"against aprivilegeddecision, andcd /srv && sudo systemctl restart apprecordedcd. That is what reached the audit log, the OTel span attributecommand.binaryand OPA'sresource.binary, so an auditor filtering the store by binary would not have found the privileged decision at all.It now names what runs under elevation —
id,systemctl— looking past exec wrappers,NAME=valueassignments and the prefix's own value-taking flags, and falling back to the prefix itself for a baresudo. Every other class still names the leading command, which is what it always meant. No decision changes:binaryis a classification input only in the read-only allowlist check, and the privileged branch returns before reaching it.HOST_KEY_MISMATCHno longer leaves the reader to guess. It stated that the key had changed and stopped there, truncating both fingerprints to twenty characters — the one comparison the reader has to make, made harder. A rebuilt server and an interception produce the identical symptom, and with nothing to separate them the available move is--insecureHostKey, which disables verification for every host and every future connection rather than for this one. The message now names both causes, shows both fingerprints in full, says to confirm out of band and how (ssh-keygen -lfon the host itself), points attrustedHostKeyfor the genuine case, and says plainly what the escape hatch costs.Credential resolution failures name the method the profile asked for. The message listed all four available methods regardless of which one
authselected, which reads as an invitation to take whichever is easiest — and the easiest is a plaintext password in the environment. It now says which method was requested and why it produced nothing (SSH_AUTH_SOCKunset,keychainEntrymissing, and so on), then orders the alternatives by how much each exposes.All three are the same defect with different surfaces: the mechanism decided correctly and then described the outcome rather than what produced it.
explainRoleDenial, the denylist refusal andAPPROVAL_DENIEDwere earlier instances.