1 unstable release
|0.1.0||Aug 26, 2022|
#1920 in Command line utilities
Webauthn is a modern approach to hardware based authentication, consisting of a user with an authenticator device, a browser or client that interacts with the device, and a server that is able to generate challenges and verify the authenticator's validity.
Users are able to enroll their own tokens through a registration process to be associated to their accounts, and then are able to login using the token which performas a cryptographic authentication.
Code of Conduct
See our code of conduct
Blockchain Support Policy
This project does not and will not support any blockchain related use cases. We will not accept issues from organisations (or employees thereof) whose primary business is blockchain, cryptocurrency, NFTs or so-called “Web 3.0 technology”. This statement does not affect the rights and responsibilities granted under the project’s open source license(s).
If you have further questions about the scope of this statement and whether it impacts you, please email webauthn at firstyear.id.au
This library consists of multiple major parts.
A safe, use-case driven api, which is defined in Webauthn-RS
The low level, protocol level interactions which is defined in Webauthn-Core-RS
Protocol bindings which are defined in Webauthn-RS-proto
The FIDO MDS (authenticator transparency) parser FIDO-MDS
We strongly recommend you use the safe api, as webauthn has many sharp edges and ways to hold it wrong!
You can test this library via our demonstration site
Or you can run the demonstration your self locally with:
cd compat_tester/webauthn-rs-demo cargo run
For additional configuration options for the demo site:
cargo run -- --help
Known Supported Keys/Harwdare
We have extensively tested a variety of keys and devices, not limited to:
- Yubico 5c / 5ci / FIPS / Bio
- TouchID / FaceID (iPhone, iPad, MacBook Pro)
- Windows Hello (TPM)
If your key/browser combination don't work (generally due to missing crypto routines) please conduct a compatability test and then open an issue so that we can resolve the issue!
Known BROKEN Keys/Harwdare
- Pixel 3a / Pixel 4 + Chrome - Does not send correct attestation certificates, and ignores requested algorithms. Not resolved.
- Windows Hello with Older TPMs - Often use RSA-SHA1 signatures over attestation which may allow credential compromise/falsification.
This library has been carefully implemented to follow the w3c standard for webauthn level 3+ processing to ensure secure and correct behaviour. We support most major extensions and key types, but we do not claim to be standards complaint because:
- We have enforced extra constraints in the library that go above and beyond the security guarantees the standard offers.
- We do not support certain esoteric options.
- We do not support all cryptographic primitive types (only limited to secure ones).
- A large number of advertised features in webauthn do not function in the real world.
This library has passed a security audit performed by SUSE product security. Other security reviews are welcome!