Petr Menšík writes:

Symlinks obviously ends with non-expected SELinux contexts. I think this is actually a bug in SELinux policy for Network Manager. Because target file has wrong selinux context.

$ ls -Z /run/NetworkManager/no-stub-resolv.conf
system_u:object_r:NetworkManager_var_run_t:s0 /run/NetworkManager/no-stub- resolv.conf
$ ls -Z /etc/resolv.conf
system_u:object_r:net_conf_t:s0 /etc/resolv.conf

Fix that by:

rm -f /etc/resolv.conf
touch /etc/resolv.conf
systemctl restart NetworkManager.service

If the file is good old plain text file, it would get permissions as it always had.

this ends up creating /etc/resolv.conf as a plain file, rather than a symlink. But, I suppose, that works too.


Attachment: pgpJGHhFNWZ24.pgp
Description: PGP signature

_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to