Reporting Security Issues
When reporting a security issue, do not create an issue or file a pull request on GitHub. Instead, disclose the issue responsibly by sending an email to email@example.com (which is inhabited only by the maintainers of the various OCI projects).
The maintainers take security seriously. If you discover a security issue, please bring it to their attention right away!
Disclosure Distribution List
This list is used to provide actionable information to multiple distribution vendors at once. This list is not intended for individuals to find out about security issues.
The information members receive on firstname.lastname@example.org must not be made public, shared, nor even hinted at anywhere beyond the need-to-know within your specific team except with the list's explicit approval. This holds true until the public disclosure date/time that was agreed upon by the list. Members of the list and others may not use the information for anything other than getting the issue fixed for your respective distribution's users.
Before any information from the list is shared with respective members of your team required to fix said issue, they must agree to the same terms and only find out information on a need-to-know basis.
In the unfortunate event you share the information beyond what is allowed by this policy, you must urgently inform the email@example.com mailing list of exactly what information leaked and to whom. A retrospective will take place after the leak so we can assess how to not make the same mistake in the future.
If you continue to leak information and break the policy outlined here, you will be removed from the list.
This is a team effort. As a member of the list you must carry some water. This could be in the form of the following:
- Review and/or test the proposed patches and point out potential issues with them (such as incomplete fixes for the originally reported issues, additional issues you might notice, and newly introduced bugs), and inform the list of the work done even if no issues were encountered.
- Help draft emails to the public disclosure mailing list.
- Help with release notes.
To be eligible for the firstname.lastname@example.org mailing list, your distribution should:
- Have an actively monitored security email alias for our project.
- Have a user base not limited to your own organization.
- Have a publicly verifiable track record up to present day of fixing security issues.
- Not be a downstream or rebuild of another distribution.
- Accept the Embargo Policy that is outlined above.
- Be willing to contribute back as outlined above.
- Have someone already on the list vouch for the person requesting membership on behalf of your distribution.
Removal: If your distribution stops meeting one or more of these criteria after joining the list then you will be unsubscribed.
Requesting to Join
New membership requests are sent to email@example.com
In the body of your request please specify how you qualify and fulfill each criterion listed in Membership Criteria.
Here is a psuedo example:
To: firstname.lastname@example.org Subject: Seven-Corp Membership to email@example.com Below are each criterion and why I think we, Seven-Corp, qualify. > 0. Have an actively monitored security alias email for our project. Yes, please subscribe firstname.lastname@example.org to the distributor's announce list. > 1. Have a user base not limited to your own organization. Our user base spans of the extensive "Seven" community. We have a slack and GitHub repos and mailing lists where the community hangs out. [links] > 2. Have a publicly verifiable track record up to present day of fixing security issues. We announce on our blog all upstream patches we apply to "Seven." [link to blog posts] > 3. Not be a downstream or rebuild of another distribution. This does not apply, "Seven" is a unique snowflake distribution. > 4. Accept the Embargo Policy that is outlined above. We accept. > 5. Be willing to contribute back as outlined above. We are definitely willing to help! > 6. Be willing and able to handle PGP-encrypted email. Yes. > 7. Have someone already on the list vouch for the person requesting membership on behalf of your distribution. CrashOverride will vouch for Acidburn joining the list on behalf of the "Seven" distribution.