File: SECURITY.md

package info (click to toggle)
cylc 8.0~a2-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, sid
  • size: 10,208 kB
  • sloc: python: 39,459; sh: 13,200; xml: 157; javascript: 78; lisp: 54; perl: 16; makefile: 12
file content (39 lines) | stat: -rw-r--r-- 1,502 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
# Security Policies and Procedures

This document outlines security procedures and general policies for the Cylc
project.

  * [Reporting a Bug](#reporting-a-bug)
  * [Disclosure Policy](#disclosure-policy)
  * [Comments on this Policy](#comments-on-this-policy)

## Reporting a Bug

The Cylc maintainers take security bugs seriously. Thank you for improving the
security of Cylc. We appreciate your efforts and responsible disclosure and
will make every effort to acknowledge your contributions.

Please report security bugs by sending an email to the lead Cylc maintainers,
[Hilary Oliver](mailto:hilary.oliver@niwa.co.nz) and [Matt
Shin](mailto:matthew.shin@metoffice.gov.uk). If a fix is needed, progress will be
recorded on Cylc repository Issue page on GitHub, and resulting new releases
will be announced on the Cylc [mail forum](mailto:cylc@googlegroups.com). 

Report security bugs in third-party modules to the person or team maintaining
the module.

## Disclosure Policy

When the Cylc maintainers receive a security bug report, they will assign it to
a primary handler. This person will coordinate the fix and release process as
follows:

  * Confirm the problem and determine the affected versions.
  * Audit code to find any potential similar problems.
  * Prepare fixes for all releases still under maintenance. These fixes will be
    released as fast as possible.

## Comments on this Policy

If you have suggestions on how this process could be improved please submit a
pull request.