Re: [CentOS] SELinux file permissions

2017-01-25 Thread Tim Smith
> Did you define my_postfixauth_private_t yourself? And if so, why? > > All my sockets inside /var/spool/postfix/private/ have the type > postfix_private_t. I don't see why you think a non-standard type would fit. > And postfix_private_t gets automatically assigned and a custom fcontext > should no

Re: [CentOS] SELinux file permissions

2017-01-24 Thread Alexander Dalloz
Am 23.01.2017 um 23:44 schrieb Tim Smith: Thanks for the pointer, will take a look down that route. Could you confirm the below is expected behaviour on Centos ? # semanage fcontext -a -t my_postfixauth_private_t "/var/spool/postfix/private(/.*)?" ValueError: Type my_postfixauth_private_t is in

Re: [CentOS] SELinux file permissions

2017-01-24 Thread Mike McCarthy, W1NR
This last update caused numerous services to stop working for me. I fixed them with a relabel. touch /.autorelabel reboot Try that and see... Mike On 01/23/2017 01:57 PM, Tim Smith wrote: > Hi, > > I'm trying to grant dovecot the ability to manage its socket within > the postfix spool directory.

Re: [CentOS] SELinux file permissions

2017-01-23 Thread Tim Smith
Thanks for the pointer, will take a look down that route. Could you confirm the below is expected behaviour on Centos ? # semanage fcontext -a -t my_postfixauth_private_t "/var/spool/postfix/private(/.*)?" ValueError: Type my_postfixauth_private_t is invalid, must be a file or device type On 23

Re: [CentOS] SELinux file permissions

2017-01-23 Thread Lukas Zapletal
Hello, restorecon works only for existing files, for new files you are looking for file transition rule. Google that out, there is plenty of articles on that topic, for example: https://fedoraproject.org/wiki/Features/SELinuxFileNameTransition LZ 2017-01-23 19:57 GMT+01:00 Tim Smith : > Hi, >