search for: restorcon

https://bugzilla.mindrot.org/show_bug.cgi?id=1933 Bug #: 1933 Summary: restorecon typoed as "restorcon" in contrib/redhat/sshd.init Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Miscell...

https://bugzilla.mindrot.org/show_bug.cgi?id=1933 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #2 from Damien Miller <djm at mindrot.org> --- Set all RESOLVED bugs to CLOSED with release

I'd like to run SELinux on my CentOS server in enforcing mode, but I get the above message when I run sealert. I assume this is because I am accessing the server from my laptop? In any case, I googled for the message, and this threw up dozens of similar queries over many years. Most of the ones I read offered methods of avoiding the problem rather than solving it. Am I right in thinking the

Hi, Spamassassin has been working nicely on my main server running CentOS 7 and Postfix. SELinux is activated (Enforcing). Since the most recent update (don't know if it's related to it though) I'm getting the following SELinux error. --8<----------------------------------------------------------------- SELinux is preventing /usr/bin/perl from 'read, write' accesses on

Hello, My problem is to add selinux policies can any help to say what is wrong with my policies I write this! semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/html(/.*)?/ typo3conf(/.*)?" I have more instances from typo3 I found this construct in the selinux policies "/var/www/html(/.*)?/uploads(/.*)?" but my is not working ? and I have only errors? neverallow

Package: xen-utils-common Version: 4.4.1-2 Severity: normal For correct operation under SE Linux the start script needs to assign correct security labels to firectories it creates. Note that restorcon doesn't cause any problems if run twice. If it's executable then you can safely run it. Below is a patch that demonstrates how to solve this problem. --- xen.old 2014-10-12 17:49:11.348923959 +1100 +++ xen 2014-10-12 17:50:49.257694941 +1100 @@ -66,6 +66,7 @@ [ -d /run/xen ] &&...

...c is telling us. We use Fail2Ban on a number of other Inetenet facing hosts. We have not yet detected anything similar on those, although until this morning's descovery we never really looked for this situation specifically. To check and see if anything was off kilter in the contexts I ran restorcon -Rv on /sbin and on /usr and restarted Fail2Ban. When I reviewed the log file I found these in /var/log/messages. setroubleshoot: [avc.ERROR] Plugin Exception restorecon #012Traceback (most recent call last):#012 File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", lin...