trezor-firmware

Commit Graph

Author	SHA1	Message	Date
matejcik	8a5cb41060	chore(core): regenerate with new templates	3 years ago
matejcik	b1e4246b46	refactor(core/webauthn): make sure KEY_AGREEMENT_*KEY is generated once per power-up This is what the spec recommends and it has been the case before workflow-restarts, when `apps.webauthn.fido2` was imported exactly once per lifetime. With workflow-restarts, `fido2` is being imported repeatedly and the keys regenerated. This does not seem to be a problem per the spec -- a FIDO workflow will retain the same keys, and non-FIDO workflows can be seen as unplugs/replugs as far as the FIDO functionality is concerned. However, regenerating the keys is slow, which is a problem for the hardware-based unit tests. We can avoid the slowness by returning to the spec-mandated behavior and generating once per power-up.	3 years ago
matejcik	5d12b943b3	feat(core): ensure all module names are interned	3 years ago

Author

SHA1

Message

Date

matejcik

8a5cb41060

chore(core): regenerate with new templates

matejcik

b1e4246b46

refactor(core/webauthn): make sure KEY_AGREEMENT_*KEY is generated once per power-up

This is what the spec recommends and it has been the case before
workflow-restarts, when `apps.webauthn.fido2` was imported exactly once
per lifetime.

With workflow-restarts, `fido2` is being imported repeatedly and the
keys regenerated. This does not seem to be a problem per the spec -- a
FIDO workflow will retain the same keys, and non-FIDO workflows can be
seen as unplugs/replugs as far as the FIDO functionality is concerned.

However, regenerating the keys is slow, which is a problem for the
hardware-based unit tests. We can avoid the slowness by returning to the
spec-mandated behavior and generating once per power-up.

matejcik

5d12b943b3

feat(core): ensure all module names are interned

3 Commits (a58823cc0c29b1b71d4e6a4af6f529817d870086)