benma

Thanks a lot for debugging. Upgrading protoc is actually on our radar. CC @Beerosagos In the meantime you can downgrade your local installation of protobuf I think.

@zerotobtc have you tried downgrading protobuf as described above? `pip3 install protobuf==3.20`. We are preparing a PR to HWI that fixes the protobuf incompatibility, but it may take a while...

Thanks for the report. Is there a legacy/compatibility mode to do it without eip712 messages as before?

Work on this has started.

We are releasing support for EIP-712 soon. The PR implementing it was merged (https://github.com/digitalbitbox/bitbox02-firmware/pull/920), v9.12.0 is [tagged](https://github.com/digitalbitbox/bitbox02-firmware/blob/firmware/v9.12.0/CHANGELOG.md#9120), and Rabby is [ready](https://github.com/RabbyHub/Rabby/releases/tag/v0.34.0).

v9.12.0 was released the same day, but I forgot to update this issue. Apologies.

In Chromium on Linux, cancelling the u2f (not fido2) registration process during the password unlock does not cancel the unlock workflow. It still works on Firefox on Linux. Haven't tested...

I rebased this PR on current master (2a8c435d) here: https://github.com/benma/bitbox02-firmware/tree/fido2 All comments of this PR still apply, I haven't changed any semantics (not deliberately, anyway).

Even in the bitbox02-rust crate, which depends on the C stuff? I've been meaning to look into https://github.com/digitalbitbox/bitbox02-firmware/pull/819 again - if that one works, is this one still needed?

A bit confused, why does rust-analyzer need to run inside Docker, is there anything special inside the Docker container? Could it also run on the host? Asking because adding it...