The Security SIG has three missions that contributors can assist with:
Contributors can work on any or all of these missions.
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.
Security issues should be reported following the procedures outlined on the Security Bugs page.
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.
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
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.
This category has the following 2 subcategories, out of 2 total.
Pages in category "Security"
The following 30 pages are in this category, out of 30 total.
- Secure Coding Training Curriculum
- Security Bugs
- Security Classifications
- Security Features
- Security Guide Audit
- Security of Embedded Software
- Archive:Security Status
- Security Status for 2002
- Security Status for 2004
- Security Status for 2005
- Security Status for2003
- Security Team FAD 2016
- Security Team Hall of Fame
- Security Team Roster
- Security Tracking Bugs