| commit | 6e3c94a63090cd0e38761550495c22f2fa79d5f0 | [log] [tgz] |
|---|---|---|
| author | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Fri Dec 03 00:04:41 2021 |
| committer | GitHub <noreply@github.com> | Fri Dec 03 00:04:41 2021 |
| tree | cb5e5d0072030559f044dd8d75064520a09056c6 | |
| parent | 391d4f02543d4ff440af00a7e532ed348e2c3ddf [diff] |
webauthn: support the minPinLength extension. (#31526) This extension[1] allows a configured site to learn the minimum PIN length set on an authenticator. This is for enterprise environments that need to enforce PIN length policies. The CTAP 2.1 specification allows a) the minimum PIN length to be increased from the usual four bytes, b) a domain to be configured that is authorised to request a report on the current minimum, and c) this extension to plumb that data back to the site. Thus, if a security key is configured to allow, say, example.com to learn the minimum PIN length, and example.com creates a credential to learn that the PIN length is $x, then it knows that the PIN length enforced when that credential is exercised is never less than that. (The only way to reduce the minimum is to reset the authenticator, but that wipes all credentials.) Chromium does not provide any mechanism for configuring the allowed domain. That has to be done manually. Intent to Ship thread: https://groups.google.com/a/chromium.org/g/blink-dev/c/VnXR-U3jROc [1] https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-20210615.html#sctn-minpinlength-extension BUG=1259760 Change-Id: Ic4230b9986c8a4215e1f80da9616a571d7b2b7c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3256056 Reviewed-by: Adam Langley <agl@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Reviewed-by: Martin Kreichgauer <martinkr@google.com> Commit-Queue: Adam Langley <agl@chromium.org> Cr-Commit-Position: refs/heads/main@{#946127} Co-authored-by: Adam Langley <agl@chromium.org>
The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.
The most important sources of information and activity are:
wpt:matrix.org matrix channel; includes participants located around the world, but busiest during the European working day.If you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
Clone or otherwise get https://github.com/web-platform-tests/wpt.
Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune (or git fetch -p && git merge).
See the documentation website and in particular the system setup for running tests locally.
The wpt command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:
wpt serve - For starting the wpt http serverwpt run - For running tests in a browserwpt lint - For running the lint against all testswpt manifest - For updating or generating a MANIFEST.json test manifestwpt install - For installing the latest release of a browser or webdriver server on the local machine.wpt serve-wave - For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.On Windows wpt commands must be prefixed with python or the path to the python binary (if python is not in your %PATH%).
python wpt [command]
Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt commands.
Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false in your working tree.
The master branch is automatically synced to wpt.live and w3c-test.org.
Save the Web, Write Some Tests!
Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.
The way to contribute is just as usual:
git checkout -b topic../wpt lint as described above.If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!