Skip to content

Releases: BryanJacobs/FIDO2Applet

v2.1.1

27 Feb 07:58

Choose a tag to compare

Fixes another statekeeping corner case in resident key handling

v2.1.0

26 Feb 19:55

Choose a tag to compare

Fixes a variety of uncommon bugs. Reported FIDO2 firmware version is now 6.

Recommended over earlier versions.

v2.0.5

05 Dec 08:48

Choose a tag to compare

Allows installing using a suffix of the FIDO2 AID.
Bumps the FW version number to 5.

v2.0.4

22 Oct 20:24

Choose a tag to compare

A variety of small bug fixes.

From this version, the applet forces the use of the official FIDO AID, due to problems getting the applet's own AID on certain smartcards.

Example installation parameters: a7050506182007190400081820091904000a1904000b00.

v2.0.0

09 Jan 23:37

Choose a tag to compare

Fully functional, compatibility-tested applet at CTAP2.1 level.

Example installation parameters for a VivoKey FlexSecure: a7050506182007190400081820091904000a1904000b00.

v1.0.0-beta4

17 Sep 03:34

Choose a tag to compare

Modulo test suite bugs, this release passes the CTAP2.1 Full Feature Profile.

It's suitable for general usage. When the test suite bugs are resolved, a 1.0 will be released.

v1.0.0-beta3

27 Aug 11:42

Choose a tag to compare

More minor bugfixes.

Starting with this applet, discoverable credentials are created dynamically; this makes their number theoretically infinite, but does lead to cards using garbage collection.

v1.0.0-beta2

11 Aug 05:59

Choose a tag to compare

Minor compatibility updates.

v1.0.0-beta1

05 Aug 09:51

Choose a tag to compare

This version implements full support for CTAP2.1 and all current extensions.

In return, it uses much more flash.

Compatibility test suite pass rate is at around 96% (100% with alwaysUv forced on). None of the failing tests are likely to represent real-world intercompatibility issues.

v1.0.0-alpha4

23 Aug 13:07

Choose a tag to compare

v1.0.0-alpha4 Pre-release
Pre-release

This release passes almost all applicable FIDO CTAP2.1 conformance tests, using version 1.7.2 of the testing tool.

It's likely the remaining failed tests (CredProtect) are themselves not compliant with the spec, as they attempt to forcibly disable the alwaysUv option despite the authenticator not declaring support for the Config instructions.