From Fedora Project Wiki
(→Training: Training info from team meeting. https://meetbot.fedoraproject.org/fedora-meeting/2016-04-21/fedora_security_team.2016-04-21-14.16.html) |
No edit summary |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
== Requirements to be met == | == Requirements to be met == | ||
=== Introduction === | === Introduction === | ||
Send the following information to the [https://lists.fedoraproject.org/mailman/listinfo/security | Send the following information to the [https://lists.fedoraproject.org/mailman/listinfo/security Security Team mailing list]. | ||
* Name (pseudonym) and FAS ID | * Name (pseudonym) and FAS ID | ||
* GPG Key Fingerprint (attach GPG public key to email) | * GPG Key Fingerprint (attach GPG public key to email) | ||
| Line 14: | Line 14: | ||
* [[Security Team Work Flow]] | * [[Security Team Work Flow]] | ||
* [[Policy_for_nonresponsive_package_maintainers|Non-Responsive Maintainer Policy]] | * [[Policy_for_nonresponsive_package_maintainers|Non-Responsive Maintainer Policy]] | ||
* [[Packaging:Guidelines| Packaging Guidelines]] (You don't need to read all of this, but you need to know how to find it) | |||
== Training == | == Training == | ||
[https://access.redhat.com/security/updates/classification Red Hat Security Classification] | * [https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/ RHEL 7 Security Guide] | ||
* [https://access.redhat.com/security/updates/classification Red Hat Security Classification] | |||
[https://cve.mitre.org/about/faqs.html CVE FAQ] | * [https://cve.mitre.org/about/faqs.html CVE FAQ] | ||
* [http://www.candlepinproject.org/presentations/pki-crash-course PKI Course] | |||
[http://www.candlepinproject.org/presentations/pki-crash-course PKI Course] | |||
== On-the-job Training == | == On-the-job Training == | ||
| Line 28: | Line 27: | ||
* Lead ticket and patch process with mentor shadowing. | * Lead ticket and patch process with mentor shadowing. | ||
[[Category:Security]] | [[Category:Security Team]] | ||
Latest revision as of 15:24, 18 February 2021
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
It is still under construction and content may change. Do not rely on the information on this page.
Requirements to be met
Introduction
Send the following information to the Security Team mailing list.
- Name (pseudonym) and FAS ID
- GPG Key Fingerprint (attach GPG public key to email)
- Interests
- Why do you want to join the Security Team?
Reading
- Security Team Mission
- Security Team Goals
- Security Team Work Flow
- Non-Responsive Maintainer Policy
- Packaging Guidelines (You don't need to read all of this, but you need to know how to find it)
Training
On-the-job Training
- Shadow mentor through a ticket and patch process.
- Lead ticket and patch process with mentor shadowing.