Skip to content

Legacy enforcement-refusal text fallback never matches an initial refusal #4057

Open

Description

@nick-potts

Found while reviewing #4056 (untangle chunk A). In core/crates/ployz/src/sdk/prepare.rs:183 with build/remote.rs:192, the fallback that matches the enforcement refusal by message text (for daemons that send no details.capability) cannot match an initial refusal: admission prefixes the message before the equality check. Main already behaves this way, so #4056 neither adds nor fixes it; its new test covers only the typed-capability path.

Impact: a build against an old daemon that refuses without a capability gets the generic refusal text, not the enforcement one.

Scores: F=2 (only old daemons that predate the capability), S=3 (wrong label on a refusal, no data or security effect). F×S=6, so filed, not fixed.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions