Skip to content

Spaces materializer honors invalidations without authority check #112

@tkuhn

Description

@tkuhn

The spaces materializer validates additions through the admin closure (an RI is only materialized if its publisher is an admin of the space), but honors removals from any npx:invalidates/retracts/supersedes edge regardless of who signed it. So a validly-signed nanopub from any agent can invalidate a space's state (DoS/griefing of the materialized view — fail-closed, no privilege escalation).

Low priority / latent today, but worth tightening before the materialized state is relied on for anything access-control-adjacent. Surfaced while fixing #110.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions