New answers tagged

0

A "temporary" label change is done via the chcon command: bash-4.2# touch freetds.conf.new bash-4.2# ls -lZ freetds.conf.new -rw-r--r--. root root unconfined_u:object_r:etc_t:s0 freetds.conf.new bash-4.2# chcon -t etc_t -u system_u freetds.conf.new bash-4.2# ls -lZ freetds.conf.new -rw-r--r--. root root system_u:object_r:etc_t:s0 freetds.conf.new ...


0

semanage fcontext -l will only return the list of file contexts that are in use. You can find the man page samba_selinux and *_selinux in the selinux-policy-devel package. Fedora 24: sudo dnf install selinux-policy-devel Red Hat Enterprise Linux 7: sudo yum install selinux-policy-devel


0

From what I can tell: $ sesearch -A -t usr_t -p read | grep 'httpd usr_t' allow httpd_t usr_t : file { ioctl read getattr execute execute_no_trans open } ; allow httpd_t usr_t : dir { ioctl read getattr lock search open } ; allow httpd_t usr_t : lnk_file { read getattr } ; Which supposedly means, that web servers are allowed to access usr_t files....


0

SELinux provides a user (unconfined_u), a role (object_r), a type (user_home_t), and a level (s0). This information is used to make access control decisions. On DAC systems, access is controlled based on Linux user and group IDs. SELinux policy rules are checked after DAC rules. SELinux policy rules are not used if DAC rules deny access first. This link ...


1

The error you see is not caused by applying samba_share_t context on /common directory. You can still try restorecon -R /common, and check selinux context is indeed changed. I believe the error originates from previous configurations.


1

try running # restorecon -rv /var/ww/



Top 50 recent answers are included