mirror of https://github.com/polhenarejos/pico-fido.git synced 2026-07-22 21:38:49 +01:00

Files

T

History

Pol Henarejos bb2764bc75 Add test results.

Signed-off-by: Pol Henarejos <pol.henarejos@cttc.es>

2026-06-29 00:40:37 +02:00

docker

Add libtss2 to runners.

2026-05-28 23:47:20 +02:00

pico-fido

Fix EA P-2, F-2, F-3.

2026-06-23 11:58:31 +02:00

build-in-docker.sh

Build EDDSA tests by default.

2025-02-21 19:07:10 +01:00

conftest.py

Fix oath aid test.

2025-11-30 19:06:15 +01:00

docker_env.sh

Upgrade to bookworm CI for fido2

2025-08-29 01:32:22 +02:00

fido-alliance-conformance-results.md

Add test results.

2026-06-29 00:40:37 +02:00

README.md

Add test results.

2026-06-29 00:40:37 +02:00

run-test-in-docker.sh

Adding test scripts

2023-03-03 01:15:01 +01:00

start-up-and-test.sh

Upgrade to bookworm CI for fido2

2025-08-29 01:32:22 +02:00

utils.py

Added support for ES256K tests.

2023-08-22 13:23:42 +02:00

README.md

Tests Documentation

This directory contains Pico Fido test code and conformance-related documentation.

FIDO Alliance conformance results

The current FIDO Alliance Conformance Test App results are documented in fido-alliance-conformance-results.md.

Those results show that the tested Pico Fido firmware passed the conformance tests captured in that report.

Important limitation

Passing the FIDO Alliance conformance tests does not mean Pico Fido is FIDO Alliance certified.

Official certification requires the separate FIDO Alliance certification process and any corresponding approval/listing from the FIDO Alliance. This documentation only states that the firmware passed the conformance tests that would be used as part of that certification path.