ToS;DR Security Policy

• Reporting a Vulnerability

• Security Announcements

• Acknowledgements

Reporting a Vulnerability

If you think you've identified a security issue in any ToS;DR Project, please
do not report the issue publicly via a mailing list, IRC, a public issue on
our issue trackers, a merge request, or any other public venue.

Instead, report a
Security Vulnerability via Service Desk or via email to security@tosdr.org. Please include as many
details as possible, including a minimal reproducible example of the issue, and
an idea of how exploitable/severe you think it is.

Do not provide a merge request to fix the issue, as there is currently no
way to make confidential merge requests on http://github.com .

If you have patches which fix the security issue, please attach them to your security vulnerability report as
patch files.

Security vulnerability reports are only visible to the reporter and the ToS;DR Staff.

The next steps are then:

• The report is triaged.

• Code is audited to find any potential similar problems.

• The fix is prepared for the most recent stable branch.

• The fix is submitted to the public repository.

• On the day the issue and fix are made public, an announcement is made on the
  public channels listed below.

• The fix will be deployed into production.

Security Announcements

Security announcements are made publicly via the Confluence Docs.

Acknowledgements

This text was partially based on the
github.com/containers security policy,
flatpak security policy,
gnome security policy.