User:SwifT/proj2wiki/test

Project Description
Hardened Gentoo is a project which oversees the research, implementation, and maintenance of security oriented projects for Gentoo Linux. We are a team of very competent individuals dedicated to bring advanced security to Gentoo with a number of subprojects.

Project Goals
Hardened Gentoo's purpose is to make Gentoo viable for highly secure, high stability production server environments. This project is not a standalone project separated from the rest of Gentoo. Instead, it is intended to be a team of Gentoo developers who are focused on delivering solutions to Gentoo that provide strong security and stability. These solutions will be available in Gentoo once they've been tested for security and stability by the Hardened team.

Developers
All developers can be reached by e-mail using nickname@gentoo.org.

Contributors
The following people although non-developer are actively contributing to the project:

Subprojects
The hardened project has the following subprojects:

Resources
Resources offered by the hardened project are:

Introduction to Hardened Gentoo ] Hardened Frequently Asked Questions ] Hardened Roadmap ] Hardened Debugging ] Using Xorg with Hardened ] Hardened Toolchain Technical Description ] PaX Quickstart Guide ] PaX Flag migration from PT_PAX to XATTR_PAX ] PaX Utils ] Grsecurity2 Quickstart Guide ] Grsecurity TPE Guide ] Capabilities Listing ] PIC Intro (beginner) ] PIC Internals (intermediate) ] PIC Fixing (advanced) ] GNU Stack Quickstart ]
 * [http://www.gentoo.org//proj/en/hardened/primer.xml
 * [http://www.gentoo.org//proj/en/hardened/hardenedfaq.xml
 * [http://www.gentoo.org//proj/en/hardened/roadmap.xml
 * [http://www.gentoo.org//proj/en/hardened/hardened-debugging.xml
 * [http://www.gentoo.org//proj/en/hardened/hardenedxorg.xml
 * [http://www.gentoo.org//proj/en/hardened/hardened-toolchain.xml
 * [http://www.gentoo.org//proj/en/hardened/pax-quickstart.xml
 * [http://www.gentoo.org//proj/en/hardened/pax-migrate-xattr.xml
 * [http://www.gentoo.org//proj/en/hardened/pax-utils.xml
 * [http://www.gentoo.org//proj/en/hardened/grsecurity.xml
 * [http://www.gentoo.org//proj/en/hardened/grsec-tpe.xml
 * [http://www.gentoo.org//proj/en/hardened/capabilities.xml
 * [http://www.gentoo.org//proj/en/hardened/pic-guide.xml
 * [http://www.gentoo.org//proj/en/hardened/pic-internals.xml
 * [http://www.gentoo.org//proj/en/hardened/pic-fix-guide.xml
 * [http://www.gentoo.org//proj/en/hardened/gnu-stack.xml
 * SELinux subproject resources* Gentoo SELinux Handbook (concepts, installation, maintenance)
 * Gentoo SELinux FAQ
 * Gentoo Hardened SELinux tutorials
 * Gentoo Hardened SELinux Development Guide
 * Reporting SELinux (policy) bugs
 * Gentoo Hardened SELinux Development Policy
 * SELinux Policy Constraints
 * Gentoo Hardened Roadmap (includes SELinux development)
 * Gentoo Hardened Support Matrices (includes SELinux)


 * Rule Set Based Access Control subproject resources* RSBAC Overview
 * RSBAC Quickstart


 * System Integrity, Compliance and Reporting subproject resources* Concepts and Introduction to Integrity
 * Using Integrity Measurement Architecture in Gentoo Linux
 * Using Extended Verification Module in Gentoo Linux
 * Advanced Intrusion Detection Environment (AIDE)
 * Linux IMA/EVM Wiki


 * Porting Tool chain and Kernel Hardening to uClibc based systems subproject resources

Herds
The hardened project maintains the following herds:

I Want to Participate
To participate in the Hardened Gentoo project first join the mailing list atgentoo-hardened@lists.gentoo.org. Next, ask if there are plans to support something that you are interested in, propose a new subproject that you are interested in, choose one of the planned subprojects to work on or simply ask if you can help with something. You can also talk to the developers and users in the IRC channel #gentoo-hardened on irc.freenode.net for more information or just to chat about the project or any subprojects.

If you think you don't have the knowledge or abilities to help, then try reading the current documents (there are always sections that can be improved or typos which we miss) and when you feel brave enough then try writing those documents you missed. Usually this only requires some internet research on your side and after some documents you'll most probably be able to help with other things you thought you weren't able to help with before.

Also, if you don't have time to actively help by contributing work we will always need testers to maintain the security and stability of the overall product. All development, testing, and productive comments and feedback will be greatly appreciated.

Acknowledgements
We would like to thank the following authors and editors for their contributions to this guide: