Bug 1463035 - SELinux denies 'entrypoint' for gdm-session-worker on /etc/gdm/PreSession/Default on boot of ostree Workstation install
SELinux denies 'entrypoint' for gdm-session-worker on /etc/gdm/PreSession/Def...
Status: NEW
Product: Fedora
Classification: Fedora
Component: ostree (Show other bugs)
27
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Colin Walters
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-19 20:54 EDT by Adam Williamson
Modified: 2017-08-15 04:44 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Williamson 2017-06-19 20:54:09 EDT
After installing from the Rawhide 20170615.n.0 Workstation ostree installer image (the most recent that works properly) and booting the installed system, this SELinux denial can be seen in the alert browser:

type=AVC msg=audit(1497919268.940:308): avc:  denied  { entrypoint } for  pid=1864 comm="gdm-session-wor" path="/etc/gdm/PreSession/Default" dev="dm-0" ino=526167 scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tcontext=system_u:object_r:etc_t:s0 tclass=file permissive=0

It appears the file is mislabelled on the ostree install: sealert reports that its correct label would be bin_t (not etc_t). Thus this may be the same as https://bugzilla.redhat.com/show_bug.cgi?id=1461978 , but I'm not sure, so reporting it separately for now.
Comment 1 Colin Walters 2017-06-19 21:05:08 EDT
99% certain it's a dupe, we'll find out tomorrow; the installer should pick up the new ostree.
Comment 2 Jan Kurik 2017-08-15 04:44:50 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

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