Bug 1596753 - Launching snapd applications changes nsswitch.conf selinux context and breaks other services
Summary: Launching snapd applications changes nsswitch.conf selinux context and breaks...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: snapd
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zygmunt Krynicki
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-29 15:46 UTC by Jason Montleon
Modified: 2019-05-28 22:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 22:37:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1612430 0 unspecified CLOSED SELinux is preventing pkla-check-auth from read access on the file /etc/authselect/nsswitch.conf. 2021-02-22 00:41:40 UTC

Internal Links: 1612430

Description Jason Montleon 2018-06-29 15:46:55 UTC
Description of problem:
When booting Fedora 28 the selinux context of /etc/authselect/nsswitch.conf is system:_u:object_r:etc_t:s0.

After running a snapd application the context changes to system:_u:object_r:unlabeled_t:s0

This causes other services to not function properly. For isntance restarting postgresql will fail with an error:

"Could not translate host name "localhost", service "5432" to address:"

Version-Release number of selected component (if applicable):
postgresql-server.x86_64   10.4-1.fc28
snapd.x86_64               2.32.4-1.fc28

How reproducible:
Always.

Steps to Reproduce:
1. Boot
2. Run a snapd application
3. Try to restart postgresql

Actual results:
postgresql fails to restart because of the incorrect selinux context of the nsswitch.conf file.

Expected results:
postgresql continues to function properly after running a snapd application

Additional info:
Rebooting gets things working again until a snapd application is run.

Comment 1 C L 2018-08-28 01:50:20 UTC
The problem is not just a change in SELinux context on /etc/authselect/nsswitch.conf.

I've observed that snapd is mounting the nsswitch file with contents different to what is configured through the authselect component/package.  In my case it breaks accessing my network printer via mDNS.

Comment 2 Ben Cotton 2019-05-02 20:49:20 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 3 Ben Cotton 2019-05-28 22:37:20 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.