An open-source implementation of FIDO2 and U2F security keys written in Rust, enabling custom hardware authentication devices.
OpenSK is an open-source implementation of a FIDO2 security key written in Rust, enabling secure two-factor authentication for websites. It supports both FIDO U2F and FIDO2 standards, allowing developers to build and customize hardware authentication devices. The project serves as a research platform and proof-of-concept for exploring security key technologies.
Security researchers, embedded systems developers, and hardware enthusiasts interested in building custom FIDO2-compliant security keys or experimenting with authentication protocols.
Developers choose OpenSK for its fully open-source approach, flexibility across multiple hardware platforms, and support for cutting-edge features like post-quantum cryptography. It provides a transparent, customizable alternative to proprietary security keys.
OpenSK is an open-source implementation for security keys written in Rust that supports both FIDO U2F and FIDO2 standards.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Implements CTAP 2.0 and has FIDO Alliance certification for the stable branch, ensuring adherence to industry authentication standards.
Can run as a Wasefire applet, Tock OS application, or library, offering flexibility for different embedded systems and research setups.
Supports multiple development boards like Nordic nRF52840 variants, allowing users to choose based on form factor and debug capabilities.
Includes experimental hybrid post-quantum cryptography implementations, as detailed in a published paper, making it a platform for cutting-edge security exploration.
Provides 3D-printable designs for custom enclosures, enabling complete DIY hardware creation from software to physical casing.
Explicitly labeled as a proof-of-concept research platform and not meant for daily use, indicating potential instability and lack of robust testing.
The develop branch, where new features are added, is not FIDO certified, posing risks for projects requiring guaranteed compliance.
Requires specific supported boards and detailed installation steps, which can be daunting for those without embedded development experience.
Hardware-accelerated cryptography via ARM CryptoCell is still in progress, currently relying on software implementations that may impact performance.