On Fri, Nov 9, 2018 at 12:56 AM Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote: > > > In my experience, no, permissive mode does not disable all of SELinux's > > blocks, and _especially_ stuff having to to with networking (including > > pipes). It's always bothered me. > > Interesting. I've not run into this problem > > Well, doing "selinux=0" on the kernel parameters at reboot will then totally disable > selinux to test. I did reboot with selinux=0 but # sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: enforcing Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 31 # A mystery! Paul _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
