On Thu, Sep 30, 2021 at 11:54:58AM +0300, Vladimir Sementsov-Ogievskiy wrote:
> 9/30/21 11:47, Richard W.M. Jones wrote:
> > Under SELinux, Unix domain sockets have two labels. One is on the
> > disk and can be set with commands such as chcon(1). There is a
> > different label stored in memory (c
9/30/21 21:37, Richard W.M. Jones wrote:
On Thu, Sep 30, 2021 at 02:00:11PM -0300, Willian Rampazzo wrote:
On Thu, Sep 30, 2021 at 5:55 AM Vladimir Sementsov-Ogievskiy
wrote:
9/30/21 11:47, Richard W.M. Jones wrote:
Under SELinux, Unix domain sockets have two labels. One is on the
disk and
On Thu, Sep 30, 2021 at 02:00:11PM -0300, Willian Rampazzo wrote:
> On Thu, Sep 30, 2021 at 5:55 AM Vladimir Sementsov-Ogievskiy
> wrote:
> >
> > 9/30/21 11:47, Richard W.M. Jones wrote:
> > > Under SELinux, Unix domain sockets have two labels. One is on the
> > > disk and can be set with command
On Thu, Sep 30, 2021 at 5:55 AM Vladimir Sementsov-Ogievskiy
wrote:
>
> 9/30/21 11:47, Richard W.M. Jones wrote:
> > Under SELinux, Unix domain sockets have two labels. One is on the
> > disk and can be set with commands such as chcon(1). There is a
> > different label stored in memory (called t
9/30/21 11:47, Richard W.M. Jones wrote:
Under SELinux, Unix domain sockets have two labels. One is on the
disk and can be set with commands such as chcon(1). There is a
different label stored in memory (called the process label). This can
only be set by the process creating the socket. When
