On 10/01/2021 09:17, Ed Greshko wrote:
On 10/01/2021 09:12, Sam Varshavchik wrote:
Doug H. writes:
>
> Created bug 1913276 to fix no-stub-resolv.conf, the selinux policy needs to
> be fixed.
Thanks for opening that bug.
Note that my outbound e-mail was being blocked by this. I am using postfix for outbound and the smtp alerts were triggering for each outbound e-mail attempt and were just queuing up until I did "sudo setenforce 0". I verified that new outbound mail was sent after that and I also "pushed" the queue with "postqueue -f" and watched the log as it drained.
I might just switch back to the regular setup so that I can have selinux enabled while waiting for the fix to this.
If you want to try to fiddle with this: I don't know how NetworkManager writes out no-stub-resolv.conf. If it creates something like 'no-stub-resolv.conf.tmp', writes it out, and then renames it to 'no-stub-resolv.conf' then finding a workaround would be tough.
But, if NetworkManager just writes out a new no-stub-resolv.conf, then fiddling the selinux context on the file might make things work again.
Until the next update to selinux-policy-targeted, I suppose, which runs a restorecon on the entire universe, and will reset it again. But at least this is something that will only need to be manually unfraked once in a while, until the policies get fixed (hopefully).
There is supposedly a way to override local policies and provide site-specific overrides for selinux contexts. Or so I heard. But selinux is very poorly documented, and is very painful to work with, and I never investigated this in the past.
When I tested reverting to the previous behavior I simply started with an empty /etc/resolv.conf.
No symlink. No selinux troubles. Everything just worked.
Just to be clear....
I simply did....
systemctl mask systemd-resolved.service
rm /etc/resolv.conf
touch /etc/resolv.conf
systemctl reboot
And now....
[egreshko@f33g ~]$ cat /etc/resolv.conf
# Generated by NetworkManager
search greshko.com
nameserver 192.168.122.1
[egreshko@f33g ~]$ ls -Zl /etc/resolv.conf
-rw-r--r--. 1 root root system_u:object_r:net_conf_t:s0 74 Jan 10 09:48 /etc/resolv.conf
---
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/users@xxxxxxxxxxxxxxxxxxxxxxx