touch-packages team mailing list archive

Thread
Date

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

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Jamie Strandboge <jamie@xxxxxxxxxx>
Date: Fri, 14 Nov 2014 20:16:53 -0000
Reply-to: Bug 1385382 <1385382@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Also affects: ubuntu-touch-customization-hooks (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: ubuntu-touch-customization-hooks (Ubuntu)
       Status: New => Triaged

** Changed in: apparmor
     Assignee: Jamie Strandboge (jdstrand) => (unassigned)

-- 
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 AppArmour 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