diff options
| author | Kevin Chyn <kchyn@google.com> | 2020-08-05 21:56:31 -0700 |
|---|---|---|
| committer | Kevin Chyn <kchyn@google.com> | 2020-08-13 13:20:00 -0700 |
| commit | e44a86b2edebe3b57c5104514dbbcb9de2856d21 (patch) | |
| tree | abe14d35633d734d29f45ca95d209817c399343e /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 86943d140fe30654be52e83e5468e287a7035e47 (diff) | |
2/n: Keep track of IBiometricsFace@1.0 challenge interruptions
IBiometricsFace@1.0 only supports a single in-flight challenge.
Currently, challenge owners paths are designed to never conflict
lifecycle-wise. However, to decouple resetLockout (which relies
on challenge) from the critical user unlock path, we need to
keep track of challenge interruptions, and notify clients when
an interruption starts/finishes.
This change only adds the infrastructure for tracking challenge
interruptions. A following change will make use of this.
Bug: 145978626
Test: Builds
Change-Id: I708312cafad29614e3708b5c606ae8a90704ac66
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions