Robin Krahl
Robin Krahl
Actually, there is a much simpler approach: have a `Mechanism::ALL` constant with the activated mechanisms. You can then iterate and match over the elements of this constant in a const...
Rebased onto main and updated so that we now only define a single list of implemented mechanisms.
@sosthene-nitrokey @daringer Can you please review this so that we can include it in the next release?
Unfortunately `paste` has been [marked as unmaintained](https://rustsec.org/advisories/RUSTSEC-2024-0436.html) since I created the first version of this PR, so using it would probably lead to problems sooner or later anyway. I’ve updated...
Not sure when this issue was fixed but with the current main, the version is updated after the firmware update.
I’ve updated nitrokey-3-firmware so that we no longer need the littlefs feature in this crate. So I’ll hold off on merging this until we have other breaking changes.
- [x] `nitrokeys/features/fido2/website` contains information specific to the Nitrokey FIDO2 (update.nitrokey.com). - [x] `nitrokeys/features/u2f/odoo` and `nitrokeys/features/u2f/2fa` list Nitrokey Pro and Storage as supported – for Odoo this might be fine...
Before we publish the rules to other repositories, we should first figure out the best rule to make it work with the libusb backend.
@nitrokey-ci test
I think there’s no reason why the CSR needs to be generated using the NetHSM API. You should be able to use `openssl req` with the PKCS11 module to generate...