Abuse filter log

From Gentoo Wiki
Abuse Filter navigation (Home | Recent filter changes | Examine past edits | Abuse log)
Jump to:navigation Jump to:search
Details for log entry 4,052

17:08, 10 May 2022: Concord (talk | contribs) triggered filter 13, performing the action "edit" on Project:SELinux. Actions taken: Tag; Filter description: New Project Member (examine | diff)

Changes made in edit

 
|Role=Documentation, Policy, Userland
 
|Role=Documentation, Policy, Userland
 
|IsLead=Yes
 
|IsLead=Yes
 +
}}{{Project Member
 +
|Developer=User:Concord
 +
|Role=Documentation, Policy
 +
|IsLead=No
 
}}
 
}}
 
}}
 
}}

Action parameters

VariableValue
Edit count of the user (user_editcount)
9
Name of the user account (user_name)
'Concord'
Age of the user account (user_age)
342487
Page ID (page_id)
15961
Page namespace (page_namespace)
510
Page title (without namespace) (page_title)
'SELinux'
Full page title (page_prefixedtitle)
'Project:SELinux'
Action (action)
'edit'
Edit summary/reason (summary)
'Add concord@g.o to members'
Old content model (old_content_model)
'wikitext'
New content model (new_content_model)
'wikitext'
Old page wikitext, before the edit (old_wikitext)
'{{Project |Name=SELinux |Description=This project manages SELinux support in Gentoo. This includes providing kernels with SELinux support, providing patches to userland utilities, writing strong Gentoo-specific default profiles, and maintaining a good default set of policies. |Email=selinux@gentoo.org |Packages=Yes |IRC=#gentoo-hardened |ParentProject=Project:Hardened |PropagatesMembers=Yes |LeadElectionDate=2019-04-29 |Members={{Project Member |Developer=User:Perfinion |Role=Documentation, Policy, Userland |IsLead=Yes }} }} [http://www.nsa.gov/research/selinux/index.shtml Security-Enhanced Linux] (SELinux) is a Mandatory Access Control system using type enforcement and role-based access control. It is integrated within Linux as a [http://lsm.immunix.org/ Linux Security Module] (LSM) implementation. In addition to the kernel portion, SELinux consists of a library (libselinux) and userland utilities for compiling policy (checkpolicy), and loading policy (policycoreutils), in addition to other user programs. One common misconception is that SELinux is a complete security solution. It is not. SELinux only provides access control on system objects. It can work well with other Hardened projects, such as PaX, for a more complete solution. == Goals == Our goal is to make SELinux (with Gentoo Hardened) available to more users. As a result, we: * Develop, improve and maintain the proper documentation and learning material for end users to master SELinux. * Maintain a stable yet progressive set of userland tools that are needed to interoperate with SELinux on a Linux system (such as the core utilities, libselinux and more). * Focus on the integration of SELinux and SELinux-awareness within the Gentoo distribution, offering the necessary feedback on Portage and other utilities. * Develop, improve and maintain a good and secure default policy, based on the reference policy, so that end users have no difficulties working with and enhancing SELinux within their environment. == Special thanks to == The following people are or have been actively contributing to the project: {| class="table table-condensed table-striped" style="text-align: left;" |- ! Contributor ! Nickname ! Role |- | Chris Richards | gizmo | Policy development, support |- | Christopher PeBenito | pebenito | Previous SELinux subproject lead, policy development, packaging and support |- | Sven Vermeulen | SwifT | Previous SELinux subproject lead, policy development, packaging and support |- | Mira Ressel | aranea | Policy development, support |- |} == Resources == Resources offered by the SELinux project include: {| class="table table-condensed table-striped" |- style="vertical-align: top; white-space: nowrap;" ! colspan=2 | User documentation |- | [[SELinux|SELinux documentation]] | The main user documentation portal on the wiki |- | [[Project:SELinux/Reporting_policy_bugs|Reporting SELinux (policy) bugs]] | A guide on writing helpful SELinux related bug reports |- | [[SELinux/Constraints|SELinux policy constraints]] | A short introduction to the constraints that are active in the SELinux policy |- ! colspan=2 | Development oriented documentation |- | [[Project:SELinux/Development|SELinux policy package development]] | How to create policy ebuilds |- | [[Project:SELinux/Development_policy|SELinux development policy]] | Policy on developing SELinux policies within Gentoo, including the principles and security models used in Gentoo Hardened |- | [[Project:SELinux/CodingStyle|Coding style]] | Coding style for SELinux policies |} == I want to participate == To participate in the SELinux project first join the mailing list at {{Mail|gentoo-hardened@gentoo.org}}. Then ask if there are plans to support something that you are interested in, propose a new sub-project that you are interested in or choose one of the planned sub-projects to work on. You may talk to the developers and users in the IRC channel {{IRC|gentoo-hardened}} on Libera.Chat for more information or just to chat about the project or any sub-projects. If you don't have the ability to actively help by contributing work we will always need testers to use and audit the SELinux policies. All development, testing, feedback, and productive comments will be greatly appreciated. === Policy submissions === The critical component of a SELinux system is having a strong policy. The team does its best to support as many daemons as possible. However, we cannot create policies for daemons with which we are unfamiliar. But we are happy to receive policy submissions for consideration. There are a few requirements: * Make comments (in the policy and/or bug), so we can understand changes from the Reference Policy example policy. * The policy should cover common installations. Please do not submit policies for odd or nonstandard daemon configurations. * We need to know if the policy is dependent on another policy (for example rpcd is dependent on portmap) other than base-policy. The policy should be submitted on [http://bugs.gentoo.org/ Bugzilla]. Please attach the {{Path|.te}} and {{Path|.fc}} files separately to the bug, not as a tarball. The bug should be Cc'ed to {{Mail|selinux@gentoo.org}} and will be properly reassigned by the team.'
New page wikitext, after the edit (new_wikitext)
'{{Project |Name=SELinux |Description=This project manages SELinux support in Gentoo. This includes providing kernels with SELinux support, providing patches to userland utilities, writing strong Gentoo-specific default profiles, and maintaining a good default set of policies. |Email=selinux@gentoo.org |Packages=Yes |IRC=#gentoo-hardened |ParentProject=Project:Hardened |PropagatesMembers=Yes |LeadElectionDate=2019-04-29 |Members={{Project Member |Developer=User:Perfinion |Role=Documentation, Policy, Userland |IsLead=Yes }}{{Project Member |Developer=User:Concord |Role=Documentation, Policy |IsLead=No }} }} [http://www.nsa.gov/research/selinux/index.shtml Security-Enhanced Linux] (SELinux) is a Mandatory Access Control system using type enforcement and role-based access control. It is integrated within Linux as a [http://lsm.immunix.org/ Linux Security Module] (LSM) implementation. In addition to the kernel portion, SELinux consists of a library (libselinux) and userland utilities for compiling policy (checkpolicy), and loading policy (policycoreutils), in addition to other user programs. One common misconception is that SELinux is a complete security solution. It is not. SELinux only provides access control on system objects. It can work well with other Hardened projects, such as PaX, for a more complete solution. == Goals == Our goal is to make SELinux (with Gentoo Hardened) available to more users. As a result, we: * Develop, improve and maintain the proper documentation and learning material for end users to master SELinux. * Maintain a stable yet progressive set of userland tools that are needed to interoperate with SELinux on a Linux system (such as the core utilities, libselinux and more). * Focus on the integration of SELinux and SELinux-awareness within the Gentoo distribution, offering the necessary feedback on Portage and other utilities. * Develop, improve and maintain a good and secure default policy, based on the reference policy, so that end users have no difficulties working with and enhancing SELinux within their environment. == Special thanks to == The following people are or have been actively contributing to the project: {| class="table table-condensed table-striped" style="text-align: left;" |- ! Contributor ! Nickname ! Role |- | Chris Richards | gizmo | Policy development, support |- | Christopher PeBenito | pebenito | Previous SELinux subproject lead, policy development, packaging and support |- | Sven Vermeulen | SwifT | Previous SELinux subproject lead, policy development, packaging and support |- | Mira Ressel | aranea | Policy development, support |- |} == Resources == Resources offered by the SELinux project include: {| class="table table-condensed table-striped" |- style="vertical-align: top; white-space: nowrap;" ! colspan=2 | User documentation |- | [[SELinux|SELinux documentation]] | The main user documentation portal on the wiki |- | [[Project:SELinux/Reporting_policy_bugs|Reporting SELinux (policy) bugs]] | A guide on writing helpful SELinux related bug reports |- | [[SELinux/Constraints|SELinux policy constraints]] | A short introduction to the constraints that are active in the SELinux policy |- ! colspan=2 | Development oriented documentation |- | [[Project:SELinux/Development|SELinux policy package development]] | How to create policy ebuilds |- | [[Project:SELinux/Development_policy|SELinux development policy]] | Policy on developing SELinux policies within Gentoo, including the principles and security models used in Gentoo Hardened |- | [[Project:SELinux/CodingStyle|Coding style]] | Coding style for SELinux policies |} == I want to participate == To participate in the SELinux project first join the mailing list at {{Mail|gentoo-hardened@gentoo.org}}. Then ask if there are plans to support something that you are interested in, propose a new sub-project that you are interested in or choose one of the planned sub-projects to work on. You may talk to the developers and users in the IRC channel {{IRC|gentoo-hardened}} on Libera.Chat for more information or just to chat about the project or any sub-projects. If you don't have the ability to actively help by contributing work we will always need testers to use and audit the SELinux policies. All development, testing, feedback, and productive comments will be greatly appreciated. === Policy submissions === The critical component of a SELinux system is having a strong policy. The team does its best to support as many daemons as possible. However, we cannot create policies for daemons with which we are unfamiliar. But we are happy to receive policy submissions for consideration. There are a few requirements: * Make comments (in the policy and/or bug), so we can understand changes from the Reference Policy example policy. * The policy should cover common installations. Please do not submit policies for odd or nonstandard daemon configurations. * We need to know if the policy is dependent on another policy (for example rpcd is dependent on portmap) other than base-policy. The policy should be submitted on [http://bugs.gentoo.org/ Bugzilla]. Please attach the {{Path|.te}} and {{Path|.fc}} files separately to the bug, not as a tarball. The bug should be Cc'ed to {{Mail|selinux@gentoo.org}} and will be properly reassigned by the team.'
Unified diff of changes made by edit (edit_diff)
'@@ -12,4 +12,8 @@ |Role=Documentation, Policy, Userland |IsLead=Yes +}}{{Project Member +|Developer=User:Concord +|Role=Documentation, Policy +|IsLead=No }} }} '
Old page size (old_size)
5254
Lines added in edit (added_lines)
[ 0 => '}}{{Project Member', 1 => '|Developer=User:Concord', 2 => '|Role=Documentation, Policy', 3 => '|IsLead=No' ]
Lines removed in edit (removed_lines)
[]
New page text, stripped of any markup (new_text)
' SELinux Description This project manages SELinux support in Gentoo. This includes providing kernels with SELinux support, providing patches to userland utilities, writing strong Gentoo-specific default profiles, and maintaining a good default set of policies. Project email selinux@gentoo.org Packages p.g.o/selinux@gentoo.org IRC channel #gentoo-hardened (webchat) Lead(s) Jason Zaman (perfinion)Documentation, Policy, Userland Last elected: 2019-04-29 Member(s) Subproject(s)(and inherited member(s)) (none) Parent Project Hardened Project listing Security-Enhanced Linux (SELinux) is a Mandatory Access Control system using type enforcement and role-based access control. It is integrated within Linux as a Linux Security Module (LSM) implementation. In addition to the kernel portion, SELinux consists of a library (libselinux) and userland utilities for compiling policy (checkpolicy), and loading policy (policycoreutils), in addition to other user programs. One common misconception is that SELinux is a complete security solution. It is not. SELinux only provides access control on system objects. It can work well with other Hardened projects, such as PaX, for a more complete solution. Contents 1 Goals 2 Special thanks to 3 Resources 4 I want to participate 4.1 Policy submissions Goals[edit | edit source] Our goal is to make SELinux (with Gentoo Hardened) available to more users. As a result, we: Develop, improve and maintain the proper documentation and learning material for end users to master SELinux. Maintain a stable yet progressive set of userland tools that are needed to interoperate with SELinux on a Linux system (such as the core utilities, libselinux and more). Focus on the integration of SELinux and SELinux-awareness within the Gentoo distribution, offering the necessary feedback on Portage and other utilities. Develop, improve and maintain a good and secure default policy, based on the reference policy, so that end users have no difficulties working with and enhancing SELinux within their environment. Special thanks to[edit | edit source] The following people are or have been actively contributing to the project: Contributor Nickname Role Chris Richards gizmo Policy development, support Christopher PeBenito pebenito Previous SELinux subproject lead, policy development, packaging and support Sven Vermeulen SwifT Previous SELinux subproject lead, policy development, packaging and support Mira Ressel aranea Policy development, support Resources[edit | edit source] Resources offered by the SELinux project include: User documentation SELinux documentation The main user documentation portal on the wiki Reporting SELinux (policy) bugs A guide on writing helpful SELinux related bug reports SELinux policy constraints A short introduction to the constraints that are active in the SELinux policy Development oriented documentation SELinux policy package development How to create policy ebuilds SELinux development policy Policy on developing SELinux policies within Gentoo, including the principles and security models used in Gentoo Hardened Coding style Coding style for SELinux policies I want to participate[edit | edit source] To participate in the SELinux project first join the mailing list at gentoo-hardened@gentoo.org. Then ask if there are plans to support something that you are interested in, propose a new sub-project that you are interested in or choose one of the planned sub-projects to work on. You may talk to the developers and users in the IRC channel #gentoo-hardened (webchat) on Libera.Chat for more information or just to chat about the project or any sub-projects. If you don't have the ability to actively help by contributing work we will always need testers to use and audit the SELinux policies. All development, testing, feedback, and productive comments will be greatly appreciated. Policy submissions[edit | edit source] The critical component of a SELinux system is having a strong policy. The team does its best to support as many daemons as possible. However, we cannot create policies for daemons with which we are unfamiliar. But we are happy to receive policy submissions for consideration. There are a few requirements: Make comments (in the policy and/or bug), so we can understand changes from the Reference Policy example policy. The policy should cover common installations. Please do not submit policies for odd or nonstandard daemon configurations. We need to know if the policy is dependent on another policy (for example rpcd is dependent on portmap) other than base-policy. The policy should be submitted on Bugzilla. Please attach the .te and .fc files separately to the bug, not as a tarball. The bug should be Cc'ed to selinux@gentoo.org and will be properly reassigned by the team.'
Parsed HTML source of the new revision (new_html)
'<div class="mw-parser-output"><table class="table table-condensed" style="width: 30em; font-size: 95%; border: 1px solid #ddd; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;"> <tbody><tr> <th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>SELinux</big> </th></tr> <tr valign="top"> <th>Description </th> <td style="text-align: justify;">This project manages SELinux support in Gentoo. This includes providing kernels with SELinux support, providing patches to userland utilities, writing strong Gentoo-specific default profiles, and maintaining a good default set of policies. </td></tr> <tr> <th><span title="Mails to member(s) listed below.">Project email</span> </th> <td><a rel="nofollow" class="external text" href="mailto:selinux@gentoo.org">selinux@gentoo.org</a> </td></tr> <tr> <th><span title="Link to packages.g.o for ebuilds maintained in gentoo.git.">Packages</span> </th> <td><span class="fa fa-cubes fa-fw"></span> <a rel="nofollow" class="external text" href="https://packages.gentoo.org/maintainer/selinux@gentoo.org">p.g.o/selinux@gentoo.org</a> </td></tr> <tr> <th><span title="The link opens an IRC client to libera.chat IRC channel.">IRC channel</span> </th> <td><span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-hardened">#gentoo-hardened</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-hardened">webchat</a></span>) </td></tr> <tr valign="top"> <th>Lead(s) </th> <td><ul><li><a href="/wiki/User:Perfinion" title="User:Perfinion">Jason Zaman</a> (perfinion)<br /><i>Documentation, Policy, Userland</i></li></ul> <br />Last elected: 2019-04-29 </td></tr> <tr valign="top"> <th>Member(s) </th> <td> </td></tr> <tr valign="top"> <th>Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small> </th> <td>(none) </td></tr> <tr> <th>Parent Project </th> <td><a href="/wiki/Project:Hardened" title="Project:Hardened">Hardened</a> </td></tr> <tr> <td colspan="2" style="border-top: 1px solid #ddd; font-size: smaller; text-align: center;"><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project listing</a> </td></tr></tbody></table> <p><a rel="nofollow" class="external text" href="http://www.nsa.gov/research/selinux/index.shtml">Security-Enhanced Linux</a> (SELinux) is a Mandatory Access Control system using type enforcement and role-based access control. It is integrated within Linux as a <a rel="nofollow" class="external text" href="http://lsm.immunix.org/">Linux Security Module</a> (LSM) implementation. In addition to the kernel portion, SELinux consists of a library (libselinux) and userland utilities for compiling policy (checkpolicy), and loading policy (policycoreutils), in addition to other user programs. </p><p>One common misconception is that SELinux is a complete security solution. It is not. SELinux only provides access control on system objects. It can work well with other Hardened projects, such as PaX, for a more complete solution. </p> <div id="toc" class="toc" role="navigation" aria-labelledby="mw-toc-heading"><input type="checkbox" role="button" id="toctogglecheckbox" class="toctogglecheckbox" style="display:none" /><div class="toctitle" lang="en" dir="ltr"><h2 id="mw-toc-heading">Contents</h2><span class="toctogglespan"><label class="toctogglelabel" for="toctogglecheckbox"></label></span></div> <ul> <li class="toclevel-1 tocsection-1"><a href="#Goals"><span class="tocnumber">1</span> <span class="toctext">Goals</span></a></li> <li class="toclevel-1 tocsection-2"><a href="#Special_thanks_to"><span class="tocnumber">2</span> <span class="toctext">Special thanks to</span></a></li> <li class="toclevel-1 tocsection-3"><a href="#Resources"><span class="tocnumber">3</span> <span class="toctext">Resources</span></a></li> <li class="toclevel-1 tocsection-4"><a href="#I_want_to_participate"><span class="tocnumber">4</span> <span class="toctext">I want to participate</span></a> <ul> <li class="toclevel-2 tocsection-5"><a href="#Policy_submissions"><span class="tocnumber">4.1</span> <span class="toctext">Policy submissions</span></a></li> </ul> </li> </ul> </div> <h2><span class="mw-headline" id="Goals">Goals</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:SELinux&amp;veaction=edit&amp;section=1" class="mw-editsection-visualeditor" title="Edit section: Goals">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:SELinux&amp;action=edit&amp;section=1" title="Edit section: Goals">edit source</a><span class="mw-editsection-bracket">]</span></span></h2> <p>Our goal is to make SELinux (with Gentoo Hardened) available to more users. As a result, we: </p> <ul><li>Develop, improve and maintain the proper documentation and learning material for end users to master SELinux.</li> <li>Maintain a stable yet progressive set of userland tools that are needed to interoperate with SELinux on a Linux system (such as the core utilities, libselinux and more).</li> <li>Focus on the integration of SELinux and SELinux-awareness within the Gentoo distribution, offering the necessary feedback on Portage and other utilities.</li> <li>Develop, improve and maintain a good and secure default policy, based on the reference policy, so that end users have no difficulties working with and enhancing SELinux within their environment.</li></ul> <h2><span class="mw-headline" id="Special_thanks_to">Special thanks to</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:SELinux&amp;veaction=edit&amp;section=2" class="mw-editsection-visualeditor" title="Edit section: Special thanks to">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:SELinux&amp;action=edit&amp;section=2" title="Edit section: Special thanks to">edit source</a><span class="mw-editsection-bracket">]</span></span></h2> <p>The following people are or have been actively contributing to the project: </p> <table class="table table-condensed table-striped" style="text-align: left;"> <tbody><tr> <th>Contributor </th> <th>Nickname </th> <th>Role </th></tr> <tr> <td>Chris Richards </td> <td>gizmo </td> <td>Policy development, support </td></tr> <tr> <td>Christopher PeBenito </td> <td>pebenito </td> <td>Previous SELinux subproject lead, policy development, packaging and support </td></tr> <tr> <td>Sven Vermeulen </td> <td>SwifT </td> <td>Previous SELinux subproject lead, policy development, packaging and support </td></tr> <tr> <td>Mira Ressel </td> <td>aranea </td> <td>Policy development, support </td></tr> </tbody></table> <h2><span class="mw-headline" id="Resources">Resources</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:SELinux&amp;veaction=edit&amp;section=3" class="mw-editsection-visualeditor" title="Edit section: Resources">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:SELinux&amp;action=edit&amp;section=3" title="Edit section: Resources">edit source</a><span class="mw-editsection-bracket">]</span></span></h2> <p>Resources offered by the SELinux project include: </p> <table class="table table-condensed table-striped"> <tbody><tr style="vertical-align: top; white-space: nowrap;"> <th colspan="2">User documentation </th></tr> <tr> <td><a href="/wiki/SELinux" title="SELinux">SELinux documentation</a> </td> <td>The main user documentation portal on the wiki </td></tr> <tr> <td><a href="/wiki/Project:SELinux/Reporting_policy_bugs" title="Project:SELinux/Reporting policy bugs">Reporting SELinux (policy) bugs</a> </td> <td>A guide on writing helpful SELinux related bug reports </td></tr> <tr> <td><a href="/wiki/SELinux/Constraints" title="SELinux/Constraints">SELinux policy constraints</a> </td> <td>A short introduction to the constraints that are active in the SELinux policy </td></tr> <tr> <th colspan="2">Development oriented documentation </th></tr> <tr> <td><a href="/wiki/Project:SELinux/Development" title="Project:SELinux/Development">SELinux policy package development</a> </td> <td>How to create policy ebuilds </td></tr> <tr> <td><a href="/wiki/Project:SELinux/Development_policy" title="Project:SELinux/Development policy">SELinux development policy</a> </td> <td>Policy on developing SELinux policies within Gentoo, including the principles and security models used in Gentoo Hardened </td></tr> <tr> <td><a href="/wiki/Project:SELinux/CodingStyle" title="Project:SELinux/CodingStyle">Coding style</a> </td> <td>Coding style for SELinux policies </td></tr></tbody></table> <h2><span class="mw-headline" id="I_want_to_participate">I want to participate</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:SELinux&amp;veaction=edit&amp;section=4" class="mw-editsection-visualeditor" title="Edit section: I want to participate">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:SELinux&amp;action=edit&amp;section=4" title="Edit section: I want to participate">edit source</a><span class="mw-editsection-bracket">]</span></span></h2> <p>To participate in the SELinux project first join the mailing list at <a rel="nofollow" class="external text" href="mailto:gentoo-hardened@gentoo.org">gentoo-hardened@gentoo.org</a>. Then ask if there are plans to support something that you are interested in, propose a new sub-project that you are interested in or choose one of the planned sub-projects to work on. You may talk to the developers and users in the IRC channel <span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-hardened">#gentoo-hardened</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-hardened">webchat</a></span>) on Libera.Chat for more information or just to chat about the project or any sub-projects. If you don't have the ability to actively help by contributing work we will always need testers to use and audit the SELinux policies. All development, testing, feedback, and productive comments will be greatly appreciated. </p> <h3><span class="mw-headline" id="Policy_submissions">Policy submissions</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:SELinux&amp;veaction=edit&amp;section=5" class="mw-editsection-visualeditor" title="Edit section: Policy submissions">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:SELinux&amp;action=edit&amp;section=5" title="Edit section: Policy submissions">edit source</a><span class="mw-editsection-bracket">]</span></span></h3> <p>The critical component of a SELinux system is having a strong policy. The team does its best to support as many daemons as possible. However, we cannot create policies for daemons with which we are unfamiliar. But we are happy to receive policy submissions for consideration. There are a few requirements: </p> <ul><li>Make comments (in the policy and/or bug), so we can understand changes from the Reference Policy example policy.</li> <li>The policy should cover common installations. Please do not submit policies for odd or nonstandard daemon configurations.</li> <li>We need to know if the policy is dependent on another policy (for example rpcd is dependent on portmap) other than base-policy.</li></ul> <p>The policy should be submitted on <a rel="nofollow" class="external text" href="http://bugs.gentoo.org/">Bugzilla</a>. Please attach the <span style="font-family: monospace; font-size: 95%">.te</span> and <span style="font-family: monospace; font-size: 95%">.fc</span> files separately to the bug, not as a tarball. The bug should be Cc'ed to <a rel="nofollow" class="external text" href="mailto:selinux@gentoo.org">selinux@gentoo.org</a> and will be properly reassigned by the team. </p> '
Unix timestamp of change (timestamp)
1652202506