chore: Update SECURITY.md #2549

Merged
Jade merged 2 commits from nex/meta/tighten-security-policy into main 2026-11-17 23:57:46 +00:00
Owner

If I get one more "Hi I've found a security vulnerability with an agent and would like to report this to you. I have read your security policy, so I won't include sensitive details in this email—where would you like me to send sensitive information?" email I might genuinely just start blocking people who waste our time with this garbage. Better to make it clear in writing.

If I get one more "Hi I've found a security vulnerability with an agent and would like to report this to you. I have read your security policy, so I won't include sensitive details in this email—where would you like me to send sensitive information?" email I might genuinely just start blocking people who waste our time with this garbage. Better to make it clear in writing.
chore: Update SECURITY.md
All checks were successful
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 3s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Checks / Prek / Check changed files (pull_request) Successful in 6s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m58s
Documentation / Build and Deploy Documentation (pull_request) Successful in 2m0s
47ded62e1e
nex requested review from Owners 2026-11-17 23:16:26 +00:00
SECURITY.md Outdated
@ -25,2 +25,3 @@
1. **Contact members of the team directly** over E2EE private message.
1. **Contact ALL members of the team directly** over E2EE private message.
Add EACH contact TO THE SAME ENCRYPTED ROOM. DO NOT MESSAGE ONLY ONE OF US, OR INDIVIDUALLY!
Owner

Caps bad.

1. **Contact _all_ members of the team** over E2EE private message on matrix.
   Add each contact to the same encrypted room. **Do not message maintainers individually**.
Caps bad. ```md 1. **Contact _all_ members of the team** over E2EE private message on matrix. Add each contact to the same encrypted room. **Do not message maintainers individually**.
Author
Owner

idk there's already a lot of bold in this area, the caps is a good contrast imo

idk there's already a lot of bold in this area, the caps is a good contrast imo
Owner

Caps IMO is both harder to read and feels like yelling, we have italics as a second form of emphasis to use in moderation.

Caps IMO is both harder to read and feels like yelling, we have italics as a second form of emphasis to use _in moderation_.
Author
Owner

i. feel like yelling. you're right though, probably not really appropriate

i. feel like yelling. you're right though, probably not really appropriate
SECURITY.md Outdated
Lines 32-34
@ -29,3 +30,5 @@
- [@ginger:gingershaped.computer](https://matrix.to/#/@ginger:gingershaped.computer)
2. **Email the security team** at [security@continuwuity.org](mailto:security@continuwuity.org). This is not E2EE, so
don't include sensitive details.
don't include sensitive details. Do not ask where to send sensitive details either: if you
got this far and need to ask where to send sensitive details, you probably don't have a
valid security report.
Owner
       don't include sensitive details. Do not ask where to send sensitive details either; that
       information is included in this security policy. We may not respond to emails that do this.
``` don't include sensitive details. Do not ask where to send sensitive details either; that information is included in this security policy. We may not respond to emails that do this. ```
ginger approved these changes 2026-11-17 23:44:14 +00:00
fix: Reword
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 7s
Checks / Prek / Check changed files (pull_request) Successful in 8s
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m14s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m20s
348a6bffb1
Jade approved these changes 2026-11-17 23:57:28 +00:00
Jade merged commit ceafc6f58d into main 2026-11-17 23:57:46 +00:00
Jade deleted branch nex/meta/tighten-security-policy 2026-11-17 23:57:46 +00:00
Jade referenced this pull request from a commit 2026-11-17 23:57:47 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No assignees
3 participants
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
continuwuation/continuwuity!2549
No description provided.