search for: zapletalovi

...ould 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 January 2017 at 19:06, Lukas Zapletal <lukas at zapletalovi.com> wrote: > 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...

On 9/24/2015 4:33 AM, Gene Cumm wrote: > On Wed, Sep 23, 2015 at 5:43 PM, Alan Sparks via Syslinux > <syslinux at zytor.com> wrote: > Although it means another round of testing, you could also consider > lpxelinux.0 which can support HTTP URLs on its own and probably > interacts differently with iPXE. I am curious about a quantifiable > description of "an odd

Hi, I'm trying to grant dovecot the ability to manage its socket within the postfix spool directory. I have added the below to file_contexts.local : /var/spool/postfix/private/dovecot-auth system_u:system_r:dovecot_t:s0 However, running "restorecon -v /var/spool/postfix/private/dovecot-auth" gives me the following error : restorecon:

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 <r.a.n.d.o.m.d.e.v.4+centos at gmail.com>: > Hi, > > I'm trying to grant dovecot the