On 07/20/2015 12:38 PM, Martin Cigorraga wrote:
> I created the file /.autorelabel (# touch /.autorelabel), set SELinux
to 'enforcing' and (/etc/sysconfig/selinux) and rebooted.
>
> May be I could do it without rebooting as stated in this question:
https://serverfault.com/questions/453137/how-can-i-do-an-selinux-filesystem-relabel-without-rebooting-first
but before landind there I was unaware of the 'fixfiles' tool :)
>
> HTH, let us know if not.
On Mon, Jul 20, 2015 at 3:31 PM jd1008 <jd1...@gmail.com
<mailto:jd1...@gmail.com>> wrote:
On 07/20/2015 12:23 PM, Martin Cigorraga wrote:
> Hello folks,
>
> It happened to me too that about a week or so ago SELinux
> automatically turned to 'Permissive' with an upgrade of
> selinux-related packages, I had to relabel everything to get things
> back to its previous state.
>
> Although I didn't delve in the issue at that moment I will keep
an eye
> on this issue should it happens again.
>
> Cheers,
> -MartÃn
>
>
>
>
>
>
>
So how did yo set it back to Enforcing?
But that is exactly what I did Ii.e. I touched .autorelabel) and
rebooted and
when the reply came thatmy selinux was set to permissive, I replied
with the contents of my /etc/sysconfig/selinux.
It is set to enforcing.
So how is it that in runtime, it is permissive???
So, I am led to believe that from the get-go, fedora has a backdoor!!
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
