Add LayoutTests to test privacy guarantee for timeouts / NOT_ALLOWED_ERROR |
|||
Issue descriptionAssert that WebAuthN operations that either return NOT_ALLOWED_ERROR or timeout are indistinguishable to prevent privacy leaks. Dependent on software security key.
,
Mar 31 2018
,
Apr 2 2018
The only thing that comes to mind - setup a normal timeout test (like the one that verifies the timeout works) and issue all the requests that should definitely return NOT_ALLOWED_ERROR and verify the error wasn't returned until we deliberately trigger the timeout.
,
Apr 2 2018
...basically, extending the existing timeout tests to cover all NOT_ALLOWED_ERROR cases. Beyond that I'm not sure what we could do.
,
Apr 3 2018
Do you mean external/wpt/webauthn/createcredential-timeout.https.html? I am afraid I removed all the other timeout-based tests. Maybe we can let the Testing API fast-forward time somehow, but I will have to think about the details.
,
Apr 3 2018
Oh, hm I guess I was thinking of the timeout unit tests here: https://cs.chromium.org/chromium/src/content/browser/webauth/authenticator_impl_unittest.cc Not quite the same thing.. Seems likely we could do this in browser tests. Not sure about layout tests.
,
Apr 13 2018
Looked into this further and I don't think this is possible. Should we close this out?
,
Apr 13 2018
Yeah, let's have unit tests with mockable time. |
|||
►
Sign in to add a comment |
|||
Comment 1 by engedy@chromium.org
, Mar 31 2018Labels: M-67 Pri-2