Robin Krahl

Replaced by https://github.com/trussed-dev/trussed/pull/205.

An alternative could be to make the trailing null byte in `Path` optional. `littlefs2` could then internally copy paths to a buffer to add the trailing null if needed.

Yeah, since rebasing onto main the CI fails, but the same commands worked before. Not sure why it fails now: ``` error: "/home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/Cargo.lock" does not exist, unable to build with...

And another rebase fixed it. :thinking:

Der Nitrokey 3 implementiert auch die `thirdPartyPayment`-Erweiterung. In der Test-Firmware ist außerdem `largeBlobKey` verfügbar. Der Link in der Issue-Beschreibung führt übrigens nur zu einem Hilfsskript. Der relevante Teil der Firmware...

The `c-stubs` feature allows you not to link against `libc` but you still need the `string.h` header because it is included by littlefs.

I think this is the right approach to get rid of the configuration constants. What do you think about using a `Config` or `StorageConfig` struct and a single `Storage::config` function...

I also thought about a trait with constants so that implementations that use constant values anyway can opt into compile-time checks of the configuration. But the generic-array requirement is not...

With this PR, `trussed` is the only crate outside of this repository that depends directly on `littlefs2`. (`admin-app` depends on `littlefs2`, but only for the `migration-tests` feature. Even the re-exports...

The refactoring itself leads to a small increase in binary size because it removes the infallible conversions from strings and byte slices. But that is more than compensated by [this...