From Fedora Project Wiki
(Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To re...")
 
No edit summary
Line 96: Line 96:
-->
-->
Adding support for the new features to selinux-policy brings better granularity for granting permissions and have subsequent security benefits.
Adding support for the new features to selinux-policy brings better granularity for granting permissions and have subsequent security benefits.
Additionally, the system can be run with the mls selinux policy: this is currently not possible as mls prevents system from starting when there are permissions unknown to the policy.


== Scope ==
== Scope ==
Line 103: Line 105:
** Ensure the system boots with the targeted policy
** Ensure the system boots with the targeted policy
** Ensure the system boots with the mls policy
** Ensure the system boots with the mls policy
** Ensure the permissions are recognized
** Ensure the permissions are recognized by the system
** Ensure there is no regression in services usage
** List of the new features:
** List of the new features:
*** [https://bugzilla.redhat.com/show_bug.cgi?id=1901957 perf_event class ]
*** [https://bugzilla.redhat.com/show_bug.cgi?id=1901957 perf_event class ]
Line 165: Line 166:
  - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
  - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
-->
-->
There's no visible change for end users with SELinux enabled.
There's no visible change for end users.


Admins and custom policy authors need to get known with the new features for services which make use of them.
Admins and custom policy authors may need to get familiar with the new features for services which make use of them.


== Dependencies ==
== Dependencies ==

Revision as of 19:49, 12 January 2021

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
Idea.png
Guidance
For details on how to fill out this form, see the documentation.


Make selinux-policy up-to-date with the latest kernel

Summary

Add new permissions, classes, and capabilities to the selinux policy so that system recognizes them and boots without an error message.

Owner

  • Name: Zdenek Pytela
  • Email: zpytela@redhat.com
  • Name: Ondrej Mosnacek
  • Email: omosnace@redhat.com


Current status

  • Targeted release: Fedora 34
  • Last updated: 2021-01-12
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Several new permissions, classes, and capabilities have been added to Linux kernel recently. The current SELinux policy does not reflect all the changes which means it does not make use of all the potential the kernel provides.


Feedback

Benefit to Fedora

Adding support for the new features to selinux-policy brings better granularity for granting permissions and have subsequent security benefits.

Additionally, the system can be run with the mls selinux policy: this is currently not possible as mls prevents system from starting when there are permissions unknown to the policy.

Scope

  • Other developers: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

Users should not be directly affected by this change.

N/A (not a System Wide Change)

How To Test

  • Boot a system and check for error messages and audit records.
  • Optionally, install and boot the selinux-policy-mls package.

N/A (not a System Wide Change)

User Experience

There's no visible change for end users.

Admins and custom policy authors may need to get familiar with the new features for services which make use of them.

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes