Build tooling to review Cargo.lock bumps
Reopening because I'm not happy with this. I want a tool that can be used to audit things before or while cargo update
is being run, something that allows more interactivity. The ideal workflow…
Keyfork signed derivation requests
Additional: Pass through a public key to encrypt the resulting private key to. Pass the new key to a different enclave.
Attestation of public keys to authenticate Keyfork shard requests
4c0521473f
docs: add security section
304b1f9baa
docs: add dependency information
WIP: keyfork-shard: traitify functionality
2e3c387ae1
docs: better info about writing types containing data
bf50e2aeac
keyfork-mnemonic-util: fixup not including smex
go over types that have data and make them return borrows by default
Build tooling to review Cargo.lock bumps