← Back to team overview

touch-packages team mailing list archive

[Bug 1385382] Re: Clock set to past confuses AppArmor cache validation

 

Yes, I'd put the workaround in place.  I can try and get this landed in
customizatoon-hooks as well if it's desired, but if the workaround is
enough, we should be good for now

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-
customization-hooks in Ubuntu.
https://bugs.launchpad.net/bugs/1385382

Title:
  Clock set to past confuses AppArmor cache validation

Status in AppArmor Linux application security framework:
  Won't Fix
Status in “ubuntu-touch-customization-hooks” package in Ubuntu:
  Triaged

Bug description:
  During initial boot sometimes clock could be set to past, which will confuse logic validating precompiled AppArmour cache, causing cache recreation.
  If time is not set correct(valid) value, even consequent boots will fail to validate cache, forcing cache recreation.

  This bug affects Initial out of the box experience, since device clock
  is set in the factory to default value, for example 0:0am 1st of
  January 2014

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1385382/+subscriptions