On Tue, Feb 2, 2021 at 10:46 PM Paul Moore wrote:
> On Tue, Feb 2, 2021 at 4:44 PM Daniel Walker (danielwa)
> wrote:
> > On Tue, Feb 02, 2021 at 04:35:42PM -0500, Paul Moore wrote:
> > > On Tue, Feb 2, 2021 at 4:29 PM Daniel Walker wrote:
> > > > From: Victor Kamensky
> > > >
> > > > To efficie
On Tue, Feb 2, 2021 at 4:44 PM Daniel Walker (danielwa)
wrote:
> On Tue, Feb 02, 2021 at 04:35:42PM -0500, Paul Moore wrote:
> > On Tue, Feb 2, 2021 at 4:29 PM Daniel Walker wrote:
> > > From: Victor Kamensky
> > >
> > > To efficiently find out where SELinux AVC denial is comming from
> > > take
On Tue, Feb 02, 2021 at 04:35:42PM -0500, Paul Moore wrote:
> On Tue, Feb 2, 2021 at 4:29 PM Daniel Walker wrote:
> > From: Victor Kamensky
> >
> > To efficiently find out where SELinux AVC denial is comming from
> > take backtrace of user land process and display it as type=UBACKTRACE
> > messag
On Tue, Feb 2, 2021 at 4:29 PM Daniel Walker wrote:
> From: Victor Kamensky
>
> To efficiently find out where SELinux AVC denial is comming from
> take backtrace of user land process and display it as type=UBACKTRACE
> message that comes as audit context for SELinux AVC and other audit
> messages
From: Victor Kamensky
To efficiently find out where SELinux AVC denial is comming from
take backtrace of user land process and display it as type=UBACKTRACE
message that comes as audit context for SELinux AVC and other audit
messages.
By default UBACKTRACE context messages are off. Needs to be e
5 matches
Mail list logo