Category:Security

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.

Communicating

E-Mail List

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

IRC

• #fedora-security^[?] - Fedora's Security SIG channel on Freenode.

Projects

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.

Communicating

IRC

• #fedora-security^[?] - Fedora's Security SIG channel on Freenode.

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.