Re: [CentOS] SELinux relabeling for a diffeerernt mount point

2022-04-01 Thread Leon Fauster via CentOS
Am 01.04.22 um 04:03 schrieb Kenneth Porter: I'm preparing a disk mounted at /mnt/tmp to later be mounted at /var/lib/BackupPC. Is there some magic invocation to get the selinux labels for the structure I create to assume the final mount point, so that I don't have to relabel it when it's

[CentOS] SELinux relabeling for a diffeerernt mount point

2022-03-31 Thread Kenneth Porter
I'm preparing a disk mounted at /mnt/tmp to later be mounted at /var/lib/BackupPC. Is there some magic invocation to get the selinux labels for the structure I create to assume the final mount point, so that I don't have to relabel it when it's finally mounted at its target location? Or is

Re: [CentOS] SELinux Relabeling

2009-09-12 Thread Jorge Fábregas
On Wednesday 09 September 2009 08:08:27 am Jorge Fábregas wrote: If I perform matchpathcon  /var/whatever I still get var_t as its default type. Then again, why it kept the httpd_sys_content_t after the relabel? I did the same test on Fedora 10 (which of course is way newer than Centos) and

Re: [CentOS] SELinux Relabeling

2009-09-12 Thread A. Kirillov
If I perform matchpathcon /var/whatever I still get var_t as its default type. Then again, why it kept the httpd_sys_content_t after the relabel? I did the same test on Fedora 10 (which of course is way newer than Centos) and it behaves different (the way I had in mind): after a

Re: [CentOS] SELinux Relabeling

2009-09-12 Thread Jorge Fábregas
On Saturday 12 September 2009 03:31:25 pm A. Kirillov wrote: Read this thread: https://www.redhat.com/archives/fedora-selinux-list/2009-July/msg00141.html Arrgh Sasha right on!!! Thanks so much! I had no idea about Customizable Types and indeed httpd_sys_content_t is one

[CentOS] SELinux Relabeling

2009-09-09 Thread Jorge Fábregas
Hello everyone, If create a folder called whatever under /var, the context is: root:object_r:var_t /var/whatever/ That's expected as it is under /var. If I then change its type: chcont -t httpd_sys_content_t /var/whatever The context looks like: root:object_r:httpd_sys_content_t