Check if keys are valid when encrypting with Shard
Duplicate transitive dependencies
- mio: update keyfork-crossterm
- generic-array: everything but sha1collisiondetection is out of date
- der: pkcs1, pkcs8, spki are out of date
- bitflags: big divide between 1.x and 2.x
mio…
305e070b93
Cargo.lock: bump multiple deps to deduplicate
7e5c7ea8fb
Cargo.lock: bump lalrpop to remove duplicate regex-syntax
63b4677b19
deny.toml: update to not use deprecated keys
1d68dd19d9
fry up some bacon
4ab1e8afa6
add docs to make clippy extra happy
a8b2814b17
make clippy happy
c36fe0a1b1
keyfork-shard: re-enable standard policy, alive check still disabled, add check for encryption keys when discovering certs
Refactor usage of
copy_to_slice
for derivation paths.
WIP: keyfork-shard: limit size of encrypted payload, can fit at max a 256 bit shard
WIP: keyfork-shard: limit size of encrypted payload, can fit at max a 256 bit shard
no longer applicable, other PRs managed this better
Rewrite porcelain handlers to use enum tuples of field structs instead of field structs
done as of keyfork-v0.2.4
Rewrite porcelain handlers to use enum tuples of field structs instead of field structs