Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify leak response recommendation #67

Merged
merged 1 commit into from
Oct 1, 2024
Merged

Clarify leak response recommendation #67

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/howto/recipes/_x11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,5 +17,5 @@
- Vendors, Coordinators, and Reporters should always be ready to immediately terminate an embargo and go public with whatever advice is available at the time that the vulnerability becomes known.
- The Vendor should accelerate their remediation development as much as possible.
- Even a simple Vendor acknowledgement that the problem is being worked on can help deployers adjust their response accordingly.
- The CERT/CC does not recommend punitive measures be taken against perceived "leakers". Vendors are of course free to choose with whom they cooperate in the future.
- The CERT/CC does not recommend punitive measures be taken against perceived "leakers". Vendors, Coordinators, and other CVD Participants are of course free to choose with whom they cooperate in the future.
- See [Disclosure Timing](../coordination/disclosure_timing.md), [Leaks](../coordination/leaks.md), and [Independent Discovery](../coordination/independent_discovery.md)