|
|
| (61 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 [[Category:Security_Team]] |
| | |
| {|width=100%
| |
| ! width=20% | IRC Channel
| |
| | {{fpchat|#fedora-security-team}}
| |
| |-
| |
| ! Mailing List
| |
| | {{fplist|security-team}} - Security Team mailing list <BR> {{fplist|security}} - General security mailing list (good for questions)
| |
| |-
| |
| ! Meetings
| |
| | TBD
| |
| <!--| Weekly at {{fpchat|#fedora-meeting}}<BR>[[Security_Team_meetings|Meeting Time]]<BR>[[Security_Team_meetings#Agenda_for_Next_Meeting|Next Meeting Agenda]] -->
| |
| |-
| |
| ! Current issues
| |
| | Critical Vulnerabilities <BR> Important Vulnerabilities <BR> Moderate Vulnerabilities <BR> Low 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.
| |
| | |
| [[Category:Security]] | |
