tree 4090c6a9d8e59e69844bf858eb9debc5f44b4fb3
parent 2656abe09895088eca25caafc3e92869217d1447
author Brian Colonna <bcolonna@google.com> 1353359148 -0500
committer Brian Colonna <bcolonna@google.com> 1353365144 -0500

Ignoring FUL unlock signal if user changed fixes b/7572354

Prior to this fix, one user could log into another user's account by
waiting for FUL to recognize them on their account, and then
switching to another account at a very precise time - after FUL has
recognized the user but before the device has unlocked.

This was caused by the FUL unlock() callback telling the device to
unlock even though the user had changed.  The fix is to only unlock
the device if the current user ID matches the user ID used to run
FUL.

Change-Id: I516b52d99ab7609b836939e4aae6e7df77a9e047