When SELinux is enabled, do not create a symbolic link to a "resolv.conf"
file outside /etc (e.g. in /var/run/NetworkManager), but instead create a
regular file in /etc.
This is to avoid creating policy permissions to read files in the other
non-standard "resolv.conf" directories for each applicat
Hello.
On Wed, 28/09/2016 at 17.44 -0400, Colin Walters wrote:
>
> On Wed, Sep 28, 2016, at 02:06 PM, Guido Trentalancia wrote:
> >
> > When SELinux is enabled, do not create a symbolic link to a
> > "resolv.conf"
> > file outside /etc (e.g. in /var/run/NetworkManager), but instead
> > create a
On Wed, Sep 28, 2016, at 02:06 PM, Guido Trentalancia wrote:
> When SELinux is enabled, do not create a symbolic link to a "resolv.conf"
> file outside /etc (e.g. in /var/run/NetworkManager), but instead create a
> regular file in /etc.
>
> This is to avoid creating policy permissions to read fi
When SELinux is enabled, do not create a symbolic link to a "resolv.conf"
file outside /etc (e.g. in /var/run/NetworkManager), but instead create a
regular file in /etc.
This is to avoid creating policy permissions to read files in the other
non-standard "resolv.conf" directories for each applicat