|
Tag: Redirect target changed |
| (57 intermediate revisions by 10 users not shown) |
| Line 1: |
Line 1: |
| The Fedora Security Team's mission is to help get security fixes into Fedora's repositories as soon as possible to help protect the end users.
| | #REDIRECT [[SIGs/Security]] |
| | |
| {|width=100%
| |
| ! width=20% | IRC Channel
| |
| | {{fpchat|#fedora-security-team}} <BR> {{fpchat|#fedora-security}}
| |
| |-
| |
| ! Mailing List
| |
| | {{fplist|security-team}} - Security Team mailing list <BR> {{fplist|security}} - General security mailing list (good for questions)
| |
| |-
| |
| ! Meetings
| |
| | [[Security_Team_meetings|Schedule and Agenda]]
| |
| |-
| |
| ! Current issues
| |
| | [https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&keywords=SecurityTracking%2C%20&keywords_type=allwords&list_id=2661454&priority=urgent&query_format=advanced Critical Vulnerabilities] <BR> [https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&keywords=SecurityTracking%2C%20&keywords_type=allwords&list_id=2661457&priority=high&query_format=advanced Important Vulnerabilities] <BR> [https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&keywords=SecurityTracking%2C%20&keywords_type=allwords&list_id=2661461&priority=medium&query_format=advanced Moderate Vulnerabilities] <BR> [https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&keywords=SecurityTracking%2C%20&keywords_type=allwords&list_id=2661462&priority=low&query_format=advanced Low Vulnerabilities] <BR> [https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&keywords=SecurityTracking%2C%20&keywords_type=allwords&list_id=2661465&priority=unspecified&query_format=advanced Unknown Vulnerabilities]
| |
| |}
| |
| | |
| == How ==
| |
| Red Hat Product Security opens bugs in response to [https://cve.mitre.org/ CVEs] that get reported by MITRE. A CVE bug is opened along with any tracker bugs that are opened against the individual packages. The tracking bug notifies the package owner of the vulnerability. Generally speaking, the package owner should follow up with upstream to obtain a patch or the fixed source to push out to the repositories.
| |
| | |
| The problem is that many package owners either don't have time or they don't understand the need of the tracking bug. That's where the Security Team comes in to help. We work with upstream to obtain the fixes and then provide them to the packagers via the tracking bug. We also work with packagers to help them get these fixes into the repositories.
| |
| | |
| == Taking ownership of tracking bugs ==
| |
| | |
| Each tracking bug we work on should have a person who owns it for several reasons. It would certainly be inefficient if the work was done twice, and collisions and misunderstandings might occur if two people tried to coordinate fix with upstream and packagers independently. For these reasons, we should indicate the fact we are working on the tracking bug by filling the Whiteboard of the bug with bugzilla login of the owner:
| |
| | |
| Whiteboard: fst_owner=<owner>
| |
| | |
| As <owner> bugzilla login should be used, as it simplifies further management: e.g. it will be easier to CC the owner on other possibly related bugs. For the list of bugzilla logins of Fedora Security Team see <FIX:link to roster>.
| |
| | |
| [[Category:Security]]
| |
