Security Response Team

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (1 revision(s))
(Remove outdated information, better document current status)
(4 intermediate revisions by 4 users not shown)
Line 1: Line 1:
The Fedora Security Response Team is currently in the creation stageThe initial purpose of the team is to track public security issues in Fedora.
+
= Overview =
 +
 
 +
Fedora uses identical processes for delivering security and non-security package fixesUnlike many other distributions that have security updates built only by members of their security teams, Fedora security updates are prepared by package maintainers.  Fedora Security Response Team aims to ensure that all known security flaws affecting components included in Fedora are reported to respective maintainers.
  
 
= Members =
 
= Members =
  
Team members, along with their primary security related interests and competencies:
+
Monitoring and reporting of the issues is currently handled by members of the [https://access.redhat.com/security/team/ Red Hat Security Response Team].
  
* JoshBressers (Team Lead)
+
= Goals =
* DennisGilmore
+
* JesseKeating
+
* Monitoring/reporting; general packaging related issues; buildsystem related issues; all supported releases
+
* ChrisRicker
+
* VilleSkyttä
+
* Monitoring/reporting; Java, Perl, Python, shell, SQL, HTML, Javascript, general packaging related issues; current FC+FE release
+
* JasonTibbitts
+
* DavidEisenstein
+
* Working with Fedora Legacy; Monitoring/reporting; RPM packaging; interfacing with Fedora Extras
+
* LukeMacken
+
* Security updates, [https://fedorahosted.org/bodhi/ bodhi] , [[LukeMacken/SecurityLiveCD|  SecurityLiveCD]]
+
* LubomirKundrak
+
* Monitoring, reporting, triaging and tracking.
+
* KevinFenzi
+
* Monitoring/reporting, EPEL security tracking.
+
  
== Goals ==
 
 
* Monitor various security information sources for potential security problems (old and new ones)
 
* Monitor various security information sources for potential security problems (old and new ones)
 
* When an issue is discovered: file appropriate bugs, alerting the maintainer of the need to patch their package.
 
* When an issue is discovered: file appropriate bugs, alerting the maintainer of the need to patch their package.
* Maintain list of fixed and unfixed security issues in a public CVS repository (similar how it is done for core)
 
* Create and post announcements for fixed packages to proper mailing lists
 
 
* Encourage and foster public discussion of various security issues and procedures via the fedora-security mailing list.
 
* Encourage and foster public discussion of various security issues and procedures via the fedora-security mailing list.
  
== Contacting ==
+
= Contacting =
Email is the best way to contact the Fedora Security Response Team.  Public requests should be sent via [[MailTo(fedora-security-list AT SPAMFREE redhat DOT com)] .  Private requests may be sent to [[MailTo(security AT SPAMFREE fedoraproject DOT org)] .
+
 
 +
Email is the best way to contact the Fedora Security Response Team.  Public requests should be sent via [mailto:security@SPAMFREE.lists.fedoraproject.org security@SPAMFREE.lists.fedoraproject.org].  Private requests may be sent to [mailto:security@SPAMFREE.fedoraproject.org security@SPAMFREE.fedoraproject.org].
 +
 
 +
= Participation =
  
=== Participation ===
+
Individuals with interest in the Security Response Team, or the Fedora security process should subscribe to the [https://admin.fedoraproject.org/mailman/listinfo/security fedora security list].  The goal of this list is to provide a public venue for the discussion of security issues and policies regarding the various Fedora projects.  Various members of the team can also be found in the #fedora-security channel on Freenode.
Individuals with interest in the Security Response Team, or the Fedora security process should subscribe to the [http://www.redhat.com/mailman/listinfo/fedora-security-list fedora security list] .  The goal of this list is to provide a public venue for the discussion of security issues and policies regarding the various Fedora projects.  Various members of the team can also be found in the #fedora-security channel on Freenode.
+
  
----
 
 
[[Category:Security]]
 
[[Category:Security]]

Revision as of 10:30, 15 November 2012

Contents

Overview

Fedora uses identical processes for delivering security and non-security package fixes. Unlike many other distributions that have security updates built only by members of their security teams, Fedora security updates are prepared by package maintainers. Fedora Security Response Team aims to ensure that all known security flaws affecting components included in Fedora are reported to respective maintainers.

Members

Monitoring and reporting of the issues is currently handled by members of the Red Hat Security Response Team.

Goals

  • Monitor various security information sources for potential security problems (old and new ones)
  • When an issue is discovered: file appropriate bugs, alerting the maintainer of the need to patch their package.
  • Encourage and foster public discussion of various security issues and procedures via the fedora-security mailing list.

Contacting

Email is the best way to contact the Fedora Security Response Team. Public requests should be sent via security@SPAMFREE.lists.fedoraproject.org. Private requests may be sent to security@SPAMFREE.fedoraproject.org.

Participation

Individuals with interest in the Security Response Team, or the Fedora security process should subscribe to the fedora security list. The goal of this list is to provide a public venue for the discussion of security issues and policies regarding the various Fedora projects. Various members of the team can also be found in the #fedora-security channel on Freenode.