With dirty storage we hit the assert. Returning an error permits to continue to
catch if the invariant is broken for normal operation while being able to
continue fuzzing with dirty storage.
* Coveralls (#339)
* Add code coverage report as part of the workflows
* Remove -Clink-dead-code which seems to be problematic
* Manually set features to avoid debug_* failing unit tests.
* Update badges
* Add libraries directory to trigger code coverage reporting.
* Fix coveralls badge not pointing to the branch
* Badges to stable branch
* Add Feitian OpenSK USB Dongle (#257)
Co-authored-by: superskybird <skybird.le@gmail.com>
* Fix `config.py` tool according to the new API of fido2 python package (#284)
* Fix fido2 API update.
Since fido2 0.8.1 the device descriptor moved to NamedTuple, breaking
our configuration tool.
Code is now updated accordingly and the setup script ensure we're
using the correct version for fido2 package.
* Make Yapf happy
* Fix missing update for fido2 0.9.1
Also split the comment into 2 lines so that the touch is not hidden
at the end of the screen.
* adds README changes, logo and certificate (#285)
* Fix broken parsing. (#317)
* Fix broken parsing.
By setting the default value before pre-parsing we ensure that the item
can't be None. As an extra safety the custom action also checks for
None.
Co-authored-by: Geoffrey <geoffrey@ftsafe.com>
Co-authored-by: superskybird <skybird.le@gmail.com>
Co-authored-by: kaczmarczyck <43844792+kaczmarczyck@users.noreply.github.com>
* Add Feitian OpenSK USB Dongle (#257)
Co-authored-by: superskybird <skybird.le@gmail.com>
* Fix `config.py` tool according to the new API of fido2 python package (#284)
* Fix fido2 API update.
Since fido2 0.8.1 the device descriptor moved to NamedTuple, breaking
our configuration tool.
Code is now updated accordingly and the setup script ensure we're
using the correct version for fido2 package.
* Make Yapf happy
* Fix missing update for fido2 0.9.1
Also split the comment into 2 lines so that the touch is not hidden
at the end of the screen.
* adds README changes, logo and certificate (#285)
Co-authored-by: Geoffrey <geoffrey@ftsafe.com>
Co-authored-by: superskybird <skybird.le@gmail.com>
Co-authored-by: kaczmarczyck <43844792+kaczmarczyck@users.noreply.github.com>
This way all users of storage can share the logic to choose between flash or RAM
storage depending on the "std" feature. This is needed because the store_latency
example assumes flash storage but is built when running `cargo test
--features=std`.
We don't need to build a production key without persistent storage. Tests and
fuzzing continue to use the std feature to use the RAM implementation (that does
sanity checks).