From Fedora Project Wiki
(added link to grammar for policy language) |
|||
| (10 intermediate revisions by 6 users not shown) | |||
| Line 18: | Line 18: | ||
== Documentation == | == Documentation == | ||
* [[SELinux/FAQ | * [http://fedoraproject.org/wiki/SELinux_FAQ FAQs] | ||
* [http://docs.fedoraproject.org/en-US/Fedora/13/html/Security-Enhanced_Linux/ Fedora 13 - Security-Enhanced Linux User Guide] | |||
* [http://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/ Fedora 13 - SELinux FAQ] | |||
* [http://docs.fedoraproject.org/en-US/Fedora/13/html/Managing_Confined_Services/ Fedora 13 - Managing Confined Services Guide] | |||
* [http://docs.fedoraproject.org/selinux-user-guide/f12/en-US/ Fedora 12 - Security-Enhanced Linux User Guide] | |||
* [http://sradvan.fedorapeople.org/SELinux_FAQ/ Fedora 12 - SELinux FAQ] | |||
* [http://docs.fedoraproject.org/selinux-managing-confined-services-guide/en-US/F11/html/ Fedora 11 - Managing Confined Services Guide] | |||
* [http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Security-Enhanced_Linux/index.html Red Hat Enterprise Linux 6 - SELinux Guide] | |||
* [http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/index.html Red Hat Enterprise Linux 4 - SELinux Guide] | * [http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/index.html Red Hat Enterprise Linux 4 - SELinux Guide] | ||
* http://www.redhat.com/magazine/001nov04/features/selinux/ | * http://www.redhat.com/magazine/001nov04/features/selinux/ | ||
| Line 27: | Line 34: | ||
* http://searchenterpriselinux.techtarget.com/columnItem/0,294698,sid39_gci1253747,00.html Five ways SELinux may surprise you | * http://searchenterpriselinux.techtarget.com/columnItem/0,294698,sid39_gci1253747,00.html Five ways SELinux may surprise you | ||
* http://www.tresys.com/selinux | * http://www.tresys.com/selinux | ||
* http://www.nsa.gov/selinux/ | * http://www.nsa.gov/research/selinux/ | ||
* [[ | * [[Selinux_grammar| Grammar for policy language]] | ||
If you want to work on formal documentation, you can use the [[Docs/Drafts/SELinux| Docs/Drafts/SELinux]] namespace. When you are done editing the draft, it can migrate to [[Docs/SELinux| Docs/SELinux]] . Doing this lends an air of formality and provides higher immutability and accountability in the wiki, as only the DocWritersGroup can edit the Docs/ namespace | If you want to work on formal documentation, you can use the [[Docs/Drafts/SELinux| Docs/Drafts/SELinux]] namespace. When you are done editing the draft, it can migrate to [[Docs/SELinux| Docs/SELinux]] . Doing this lends an air of formality and provides higher immutability and accountability in the wiki, as only the DocWritersGroup can edit the Docs/ namespace | ||
[[Category:SELinux]] | |||
Revision as of 06:31, 27 December 2010
Fedora SELinux Project Pages
- Understanding SELinux
- Discussion of Policies
- Troubleshooting SELinux
- Multi Category Security/MCS
- Multi Level Security/MLS
- Loadable Modules
- Policy Generation Tools
- Troubleshoot Tool
Topics
Documentation
- FAQs
- Fedora 13 - Security-Enhanced Linux User Guide
- Fedora 13 - SELinux FAQ
- Fedora 13 - Managing Confined Services Guide
- Fedora 12 - Security-Enhanced Linux User Guide
- Fedora 12 - SELinux FAQ
- Fedora 11 - Managing Confined Services Guide
- Red Hat Enterprise Linux 6 - SELinux Guide
- Red Hat Enterprise Linux 4 - SELinux Guide
- http://www.redhat.com/magazine/001nov04/features/selinux/
- http://www.redhat.com/magazine/006apr05/features/selinux/
- http://www.redhatmagazine.com/2007/05/04/whats-new-in-selinux-for-red-hat-enterprise-linux-5/
- http://www.redhat.com/v/swf/SELinux/ - DanielWalsh (Red Hat SELinux developer)'s Flash presentation.
- http://danwalsh.livejournal.com/ - DanielWalsh blog which has a continous discourse on understanding and using SELinux. Check other posts.
- http://searchenterpriselinux.techtarget.com/columnItem/0,294698,sid39_gci1253747,00.html Five ways SELinux may surprise you
- http://www.tresys.com/selinux
- http://www.nsa.gov/research/selinux/
- Grammar for policy language
If you want to work on formal documentation, you can use the Docs/Drafts/SELinux namespace. When you are done editing the draft, it can migrate to Docs/SELinux . Doing this lends an air of formality and provides higher immutability and accountability in the wiki, as only the DocWritersGroup can edit the Docs/ namespace