nsaspy/zara-plugins
1
0
Fork 0
Code Issues 10 Pull requests 297 Projects Releases Packages Wiki Activity Actions

Security: filter Discord public output for private-data leaks #491

Open
nsaspy wants to merge 0 commits from rage/30-discord-public-output-privacy into main
pull from: rage/30-discord-public-output-privacy
merge into: nsaspy:main
Conversation 0 Commits - Files changed -
nsaspy commented 2026-09-08 02:20:11 +00:00
Owner
Copy link

Fixes #30.

TDD starts at dd06a37ccf5ea5ad35df454dc5e5a92572614d54 with a RED contract for Discord's public/untrusted boundary and fail-closed filtering of obvious operator-profile, memory-dump, credential, token, and authorization disclosures.

Implementation adds a small stdlib-only public-output filter at the Discord delivery boundary. Blocked output is replaced with a fixed safe refusal before it enters Discord history or public delivery; normal answers remain unchanged. The plugin explicitly defines Discord as PUBLIC/UNTRUSTED defense-in-depth context.

This does not claim to replace Zara Core principal/tool/memory capability isolation. Core remains the authority for preventing public turns from acquiring private data in the first place; this plugin slice only reduces accidental public disclosure at the final Discord boundary.

Exact-head gates required before merge: registry validator, zara-discord unit suite, generated pinned-Zara compatibility, package/runtime-layout checks, and nix flake check.

Fixes #30. TDD starts at `dd06a37ccf5ea5ad35df454dc5e5a92572614d54` with a RED contract for Discord's public/untrusted boundary and fail-closed filtering of obvious operator-profile, memory-dump, credential, token, and authorization disclosures. Implementation adds a small stdlib-only public-output filter at the Discord delivery boundary. Blocked output is replaced with a fixed safe refusal before it enters Discord history or public delivery; normal answers remain unchanged. The plugin explicitly defines Discord as PUBLIC/UNTRUSTED defense-in-depth context. This does not claim to replace Zara Core principal/tool/memory capability isolation. Core remains the authority for preventing public turns from acquiring private data in the first place; this plugin slice only reduces accidental public disclosure at the final Discord boundary. Exact-head gates required before merge: registry validator, zara-discord unit suite, generated pinned-Zara compatibility, package/runtime-layout checks, and `nix flake check`.
Some checks failed
CI / test (pull_request) Failing after 18s
Details
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/30-discord-public-output-privacy:rage/30-discord-public-output-privacy
git switch rage/30-discord-public-output-privacy

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff rage/30-discord-public-output-privacy
git switch rage/30-discord-public-output-privacy
git rebase main
git switch main
git merge --ff-only rage/30-discord-public-output-privacy
git switch rage/30-discord-public-output-privacy
git rebase main
git switch main
git merge --no-ff rage/30-discord-public-output-privacy
git switch main
git merge --squash rage/30-discord-public-output-privacy
git switch main
git merge --ff-only rage/30-discord-public-output-privacy
git switch main
git merge rage/30-discord-public-output-privacy
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
accessibility
Barrier affecting people with disabilities

  
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
security

   
wontfix
This will not be worked on

No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
security
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/zara-plugins!491
No description provided.