|
Tag: Redirect target changed |
| (46 intermediate revisions by 8 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] <BR> [https://bugzilla.redhat.com/buglist.cgi?bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&classification=Fedora&keywords=SecurityTracking%2C%20&keywords_type=allwords&list_id=2719448&priority=unspecified&priority=urgent&priority=high&priority=medium&priority=low&query_format=advanced Bugs in MODIFIED, ON_DEV, ON_QA states]
| |
| |}
| |
| | |
| == 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.
| |
| | |
| === Work Flow ===
| |
| # Find a bug (use one of the above links to find an open bug)
| |
| # [[Security_Team#Taking_ownership_of_tracking_bugs|Own the bug]]
| |
| # Determine if the vulnerability is already fixed in Fedora by examining the current version and/or talking with the packager
| |
| # Work with upstream to obtain a patch or version where fixed
| |
| # Work with packager to get patch or fixed version packaged and pushed as a security update
| |
| # Close bug when vulnerability is addressed in Fedora repos.
| |
| # Do a little dance.
| |
| # GOTO 1
| |
| | |
| == 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>,[<owner2>,<owner3>]
| |
| | |
| As <owner> FAS ID should be used, as it simplifies further management.. For the list of bugzilla logins of Fedora Security Team see the [[Security Team Roster]].
| |
| | |
| For multiple FST owners FAS IDs should be comma-separated and NOT contain spaces.
| |
| | |
| == Hall of Fame ==
| |
| | |
| [[Security Team Hall of Fame]]
| |
| | |
| [[Category:Security]]
| |
