Jean-Michel Picod

We selected the Nordic chip because it natively supports secure cryptographic acceleration, supports the three transport protocols described in the FIDO2 specification (USB, NFC and BLE) and has affordable development...

That's what I've been using since August to talk to the CryptoCell. There are a few differences between CC310 and CC312 though which need to be addressed. My current understanding...

Although for test/debug purposes I don't see objections to a storage serialized on drive, for a "normal" usage, I'd prefer to see the file at least encrypted and if possible...

Anyway, due to recent changes on Github, the workflow for Clippy must be adjusted for it to work properly. It now must be split into 2 workflows: an untrusted one...

If you use a vendor specific command (like we did for our `configure.py` script) to dump the storage, this should at least come with the step of validating the user's...

This means we should really go for 2 branches: - on `dev` branch the workflow should reset + compile twice in a row and ensure that the hashes are the...

As suggested during the review of PR #49, we should also: - Add linter for python and markdown - Check for proper formatting of python and markdown files

NFC support cannot happen on the Nordic dongle for 2 main reasons: * there is no antenna and therefore this would require additional electronics to be soldered on it (antenna...

It's not because the Nordic chip supports wireless protocols that they are enabled. At the moment they're not. Should we want to support them in the future, it's convenient to...

The LPC55S69 is still a Cortex-M chip so it's definitely possible to run Tock on it and then OpenSK. But because the chip is currently not supported out of the...