Bug 1884908 - Confined users fail to use grub2-set-bootf
Summary: Confined users fail to use grub2-set-bootf
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 32
Hardware: noarch
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1767779
TreeView+ depends on / blocked
 
Reported: 2020-10-03 12:37 UTC by malsworn_deliquesces
Modified: 2021-05-25 18:35 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-25 18:35:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description malsworn_deliquesces 2020-10-03 12:37:21 UTC
Description of problem:
I have confined all my users using SELinux. My main user has the staff_t context and my two other users the user_t context. Now every boot I get three errors about grub2-set-bootf not being able to write to the grub2 dir.

Version-Release number of selected component (if applicable):
selinux-policy-targeted-3.14.5-43.fc32.noarch but also tested with *-44*

How reproducible:
Happens every boot

Steps to Reproduce:
1. Confine user to a context that is not unconfined (staff_t or user_t)
2. (Re)boot system
3. Check logs using journalctl -p err -xe

Actual results:
I get the errors:

type=AVC msg=audit(1601724737.248:250): avc:  denied  { write } for  pid=975 comm="grub2-set-bootf" name="grub2" dev="vda1" ino=132254 scontext=staff_u:staff_r:staff_t:s0-s0:c0.c1023 tcontext=system_u:object_r:boot_t:s0 tclass=dir permissive=0
type=AVC msg=audit(1601724872.432:326): avc:  denied  { write } for  pid=1182 comm="grub2-set-bootf" name="grub2" dev="vda1" ino=132254 scontext=user_u:user_r:user_t:s0 tcontext=system_u:object_r:boot_t:s0 tclass=dir permissive=0

the user_t shows up twice

Expected results:
If every user should be able to write to this then I think it should be included in the policy. I assume this, because every user tries this at every boot.

Comment 1 Fedora Program Management 2021-04-29 17:19:40 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2021-05-25 18:35:22 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.