SecurityTeam
Differences between revisions 1 and 17 (spanning 16 versions)
1418
Comment: template buildout
|
1055
converted to 1.6 markup
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
[[Include(BuildingCommunity/SampleTeam/Header)]] | <<Include(SecurityTeam/Header)>> |
Line 3: | Line 3: |
||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| | ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''<<BR>><<TableOfContents>>|| |
Line 7: | Line 7: |
## Describe: ## the teams's purpose and community role ## the team tasks and work ## who might be interested in joining/getting involved with the team |
|
Line 12: | Line 8: |
= Contact = ## List the contact information of the team: Mailing-list, IRC channel and Web Forum as they may apply. Provide a link to the Launchpad page as a Team Member list if applicable. Consider how people will get in touch with you based on the contact information you supply. |
The Ubuntu Security Team represents multiple teams of people dedicated to keeping Ubuntu secure, and contributing to its proactive hardening. |
Line 15: | Line 10: |
= How to Contribute = ## Describe easy ways to contribute to the team. These should look a lot like the bulleted points on the ContributeToUbuntu wiki page. Link to more detailed subpages as necessary. |
== Projects == To discuss any Security Team projects, send email to the ubuntu-hardened mailing list. |
Line 18: | Line 13: |
= Projects = ## List the team's current projects and tasks as well as status and contact persons for each one. Make it easy for new people to know who to ask and where to go to get involved with a specific project. |
* CVE handling * tracking: Ubuntu CVE Tracker * fixing: main and universe * Hardening * Mandatory Access Control * [[AppArmor]] * [[SELinux]] * Compiler flags ([[Security/HardeningWrapper| HardeningWrapper]]) * pbuilder integration * sbuild integration * Auditing and Penetration Testing |
Line 21: | Line 26: |
= Launchpad Membership Policy = ## Describe your Launchpad team membership policy here. = Meetings = ## Link to Meeting Agendas and old meeting summaries here. |
Seem like fun? Head to the [[/GettingInvolved]] page to found out how to contribute to the SecurityTeam. |
Line 28: | Line 29: |
'''Sub-pages :''' [[Navigation(children,1)]] | '''Sub-pages :''' <<Navigation(children,1)>> |
Contents Contents |
Introduction
The Ubuntu Security Team represents multiple teams of people dedicated to keeping Ubuntu secure, and contributing to its proactive hardening.
Projects
To discuss any Security Team projects, send email to the ubuntu-hardened mailing list.
- CVE handling
- tracking: Ubuntu CVE Tracker
- fixing: main and universe
- Hardening
- Mandatory Access Control
Compiler flags (HardeningWrapper)
- pbuilder integration
- sbuild integration
- Auditing and Penetration Testing
Seem like fun? Head to the /GettingInvolved page to found out how to contribute to the SecurityTeam.
Sub-pages :
SecurityTeam (last edited 2017-01-25 23:50:10 by emilyr)