From Fedora Project Wiki

(Added links to the three missions.)
(→‎Security Response: Moved text to Security_Bugs)
Line 46: Line 46:
Security issues should be reported following the procedures outlined on the [[Security Bugs]] page.
Security issues should be reported following the procedures outlined on the [[Security Bugs]] page.
=== Security Issues Classification ===
So what counts a security issue in Fedora? Find answers in the [[Security Classifications]] page.
=== Security Features ===
Security features available in Fedora is explained on [[Security Features]] page.
=== Fedora Security Response ===
The Fedora [[Security/ResponseTeam|Security Response Team]] handles security issues within Fedora. Red Hat Product Security can be reached by mailing secalert AT redhat DOT com.
=== Endemic Security Risks  ===
Due to the Fedora Project's use of resources not directly under our control, such as mirrors, Fedora and its users have exposure to [[Mirror_manager_security_risks|additional endemic risks]], and takes as many steps as possible mitigate these risks.
=== Fedora Security Advisories ===
* [ Fedora Security Errata]
=== Fedora Security Tracking Bugs ===
* To track security vulnerabilities in packages, [[Security/TrackingBugs|tracking bugs]] are used.
=== List of Embedded Software ===
* We are maintaining a list of embedded software within various packages.  This will help us to quickly identify if a problem in library X can be corrected with updating library X, or if it also requires updating other packages that may contain their own private copies of library X.  The [[Security_of_Embedded_Software|embedded software list]] is used for this purpose.
=== List of SUID / SGID executables ===
* We are maintaining a list of SUID / SGID bit equipped executables within various packages. This will help us to quickly identify privileged binaries. This list is preliminary planned to be prepared for Fedora release of 14 and it will be enhanced later to include list of privileged binaries in also in newer versions of Fedora. The [[Set_User_Group_ID_Executables| list of SUID SGID executables]] is used for this purpose.

Revision as of 19:26, 9 November 2015

The Security SIG has three missions that contributors can assist with:

  1. Secure Coding
  2. Code Auditing
  3. Security Response

Contributors can work on any or all of these missions.

Secure Coding

Secure coding is writing code with security in mind from the beginning. By not making security mistakes the code is more secure and time won't be wasted down the road having to rewrite or redesign features and functionality.


E-Mail List

  • Fedora security list: For discussion about improvement of Fedora security.



Defensive Coding book

The Defensive Coding book is published on the Fedora Docs website and is under development. The purpose of the book is to document common mistakes developers make and help educate developers on how to better their code from the beginning.

Training and Articles

In addition to the Defensive Coding book the Security SIG is charged with creating training resources. Videos and smaller articles on secure development can also be created to concentrate specific topics. These resources should be stored in the secure coding git repository.

Security Basics and HOWTO Articles

Basic Fedora security HOWTO is SecurityBasics

Code Auditing

Many security vulnerabilities are found with the help of a code audit. If you are interested in performing an audit please see our auditing resource page.



Security Response

The Security Team helps packagers fix security vulnerabilities in packages they maintain. Most of these vulnerabilities come from the open source software community and packagers are notified by a ticket in Bugzilla.

Fedora Security Response Procedures

Security issues should be reported following the procedures outlined on the Security Bugs page.