Bug: https://bugs.launchpad.net/bugs/1322778
Between the apparmor 2.8.2 and 2.8.3, a bug was fixed in mod_apparmor
(in 2.8 revno 2120) that corrected the storage location for
AADefaultHatName. The incorrect storage caused the hat specified by
the AADefaultHatName keyword to be the default value f
Bug: https://bugs.launchpad.net/bugs/1322778
In trunk revno 2335, a bug was fixed in mod_apparmor that corrected
the storage location for AADefaultHatName. The incorrect storage
caused the hat specified by the AADefaultHatName keyword to be the
default value for AAHatName, and meant that if both
On Thu, Jun 12, 2014 at 02:23:46PM -0700, Steve Beattie wrote:
> Bug: https://bugs.launchpad.net/bugs/1322778
>
> In trunk revno 2335, a bug was fixed in mod_apparmor that corrected
> the storage location for AADefaultHatName. The incorrect storage
> caused the hat specified by the AADefaultHatNa
On 06/12/2014 05:46 PM, Seth Arnold wrote:
> On Thu, Jun 12, 2014 at 02:23:46PM -0700, Steve Beattie wrote:
>> Bug: https://bugs.launchpad.net/bugs/1322778
>>
>> In trunk revno 2335, a bug was fixed in mod_apparmor that corrected
>> the storage location for AADefaultHatName. The incorrect storage
On Thu, Jun 12, 2014 at 05:46:44PM -0700, Seth Arnold wrote:
> On Thu, Jun 12, 2014 at 02:23:46PM -0700, Steve Beattie wrote:
> > Bug: https://bugs.launchpad.net/bugs/1322778
> >
> > In trunk revno 2335, a bug was fixed in mod_apparmor that corrected
> > the storage location for AADefaultHatName.
On Thu, Jun 12, 2014 at 06:12:09PM -0700, John Johansen wrote:
> The problem is that mod_apparmor had a behavior that all profiles developed
> for it depend on.
It's not true for *all* mod_apparmor profiles — I personally make
use of AAHatName's features on a couple of different host — but yes,
I
