Michal Privoznik wrote:
> On 02/03/2017 06:32 PM, Jim Fehlig wrote:
>> If the apparmor security driver is loaded/enabled and domain config
>> contains a element whose type attribute is not 'apparmor',
>> starting the domain fails when attempting to label resources such
>> as tap FDs.
>>
>> Many
On 02/03/2017 06:32 PM, Jim Fehlig wrote:
> If the apparmor security driver is loaded/enabled and domain config
> contains a element whose type attribute is not 'apparmor',
> starting the domain fails when attempting to label resources such
> as tap FDs.
>
> Many of the apparmor driver entry
Hi, Jim,
On Thu, Feb 09, 2017 at 09:30:16AM -0700, Jim Fehlig wrote:
> Guido Günther wrote:
> > On Fri, Feb 03, 2017 at 10:32:12AM -0700, Jim Fehlig wrote:
> >> If the apparmor security driver is loaded/enabled and domain config
> >> contains a element whose type attribute is not 'apparmor',
> >>
Guido Günther wrote:
> On Fri, Feb 03, 2017 at 10:32:12AM -0700, Jim Fehlig wrote:
>> If the apparmor security driver is loaded/enabled and domain config
>> contains a element whose type attribute is not 'apparmor',
>> starting the domain fails when attempting to label resources such
>> as tap
On Fri, Feb 03, 2017 at 10:32:12AM -0700, Jim Fehlig wrote:
> If the apparmor security driver is loaded/enabled and domain config
> contains a element whose type attribute is not 'apparmor',
> starting the domain fails when attempting to label resources such
> as tap FDs.
>
> Many of the
If the apparmor security driver is loaded/enabled and domain config
contains a element whose type attribute is not 'apparmor',
starting the domain fails when attempting to label resources such
as tap FDs.
Many of the apparmor driver entry points attempt to retrieve the
apparmor security label
