fix: stuur kwetsbaarheidsmeldingen naar het adres dat we zelf documenteren #523
No reviewers
Labels
No labels
accepted
bug
declined
docs
duplicate
enhancement
good first issue
in-progress
needs-info
privacy
security
triage
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
LibreKAT/Ocideck!523
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/meldadres-consistentie"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
.github/ISSUE_TEMPLATE/config.ymlsent security reports tosecurity@vigilis.nl, whileSECURITY.mdandCODE_OF_CONDUCT.mdboth namesecurity@librekat.nl. Anyone following the tracker's own "report privately" link mailed an address the project does not document — on the one path a vulnerability reporter actually walks.Closes #507
Changes
test/security_contact_consistency_test.dart— compares everysecurity@address in the READMEs, the code of conduct,CONTRIBUTINGand all four GitHub templates against the one inSECURITY.md. A second assertion pins the canonical address to the foundation domain, so the mismatch cannot be "fixed" by draggingSECURITY.mdto the wrong address instead..github/ISSUE_TEMPLATE/config.yml— corrected tosecurity@librekat.nl.The two commits are deliberately split: the test commit stands red on its own (verified by checking it out and running it), the fix commit turns it green. The guard was also verified against a planted regression.
Gates
make check— green (86.2% line coverage, per-file floor 0 below budget).make check-secrets— red, pre-existing. trufflehog flags.git/logs/HEAD, the local reflog, as aLokaliseToken; both gitleaks passes report no leaks. Filed as #522. Not caused by this branch.make sast— red, pre-existing.semgrep.ocideck-subproces-buiten-de-gitlaagfires onlib/services/disk_traces.dart:257, which is onmainand untouched here. Filed as #521.Principles
Touches a public promise (where to report a vulnerability), so weighed against the project's principles: this moves the promise towards what the documentation already says rather than adding a new one, and puts the contact on a domain the foundation controls. No conflict to record.