Skip to content

CMDB cross-check: hostile control-character report fixture; consider --no-augments #59

Open

Description

@djbclark

Two follow-ups to the CMDB cross-check in bundle common tendcf_cmdb (policy/tendcf_services.cf, #42):

  1. Reports sanitise untrusted key, id and section text: characters outside [A-Za-z0-9._:@/-] become ?, and names are cut to 64 characters. PR 42 adds a long-key report regression. No runtime fixture yet feeds control characters (newline, ESC) through a refused key, id or section, so the sanitisation is established by source reading only. Add that hostile-text fixture.
  2. Defence in depth: consider --no-augments at the installed entry point, so a def.json cannot add variables or classes at all. This needs an explicit decision for any host that relies on augments today. No host inventory audit has been done.

From the round-3 frontier review of PR 42 (C3).

🤖 Generated with Claude Code

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