New issue
Advanced search Search tips

Issue 831995 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

authpolicy: Set timestamp that won't run backwards

Project Member Reported by ljusten@chromium.org, Apr 12 2018

Issue description

Right now we're setting base::Time::Now() in authpolicy.cc, but that depends on the system clock and can run backwards. For policy validation, though, we need a timer that can never run backwards. That way, we could validate that no old version of a policy is used.

 

Sign in to add a comment