[apparmor] [Bug 731184] Re: apparmor_parser fails to consider its own time stamp when determining if profile cache is stale

[Steve Beattie]

Fixed in commit http://bazaar.launchpad.net/~apparmor-
dev/apparmor/master/revision/1679 (pre 2.6 branching from trunk, but
post 2.6.0 release).

** Also affects: apparmor/2.6
   Importance: Undecided
       Status: New

** Changed in: apparmor
       Status: Triaged => Fix Released

** Changed in: apparmor/2.6
       Status: New => Fix Committed

** Changed in: apparmor/2.6
   Importance: Undecided => Medium

** Changed in: apparmor/2.6
    Milestone: None => 2.6.1

** Changed in: apparmor
    Milestone: 2.6.1 => None

-- 
You received this bug notification because you are a member of AppArmor
Developers, which is the registrant for AppArmor.
https://bugs.launchpad.net/bugs/731184

Title:
  apparmor_parser fails to consider its own time stamp when determining
  if profile cache is stale

Status in AppArmor Linux application security framework:
  Fix Released
Status in AppArmor 2.6 series:
  Fix Committed

Bug description:
  If the apparmor_parser is updated (outside of current packaging), when
  doing profile loads it will use the existing cache of compiled
  profiles, instead of forcing a recompile on profiles.

  This can cause apparmor to load bad policy if the parser contains a
  bug fix for the previous version of the parser.

  This can be worked around in packaging by invalidating the cache and
  forcing a profile reload when the parser is upgraded.