Tag Info

New answers tagged

2

You might want to run fixfiles -R openvpn restore An ls -alZ should give you something like this (showing your files are in the correct selinux context now): [root@server openvpn]# ls -alZ /etc/openvpn/ drwxr-xr-x. root root system_u:object_r:openvpn_etc_t:s0 . drwxr-xr-x. root root system_u:object_r:etc_t:s0 .. drwxr-xr-x. root root ...


-1

try sestatus if permissive or active, you sould have file on it (on /selinux dir). if disabled diectory shouldn't be there. disabling is done bu editing /etc/selinux/config setting SELINUX=disabled and reboot.


3

Don't do this, the directory is owned by libselinux1 and some packages depend on it. You should not remove files or directories provided by the package manager. Proven on my Debian system (7.6) To find out, which package owns a path on your system, use $ dpkg -S /selinux/ libselinux1:amd64: /selinux $ sudo apt-get remove libselinux1 ..... The following ...


0

I've been having this exact same issue on CentOS 7. After hours of trying to figure it out. I turned off SELinux and it worked. So the issue it certainly SELinux. To see if its enforcing type: getenforce To turn it completely off just type: setenforce 0


1

net.ipv4.tcp_syncookies=1 Helps in preventing SYN flood attack on the system. A value of 0 will disable it.From security point of view, it is ideal to keep it on i.e. set value to 1. However, its pretty safe to turn it off.



Top 50 recent answers are included