Cryptography self-check at startup
Open
@tgeoghegan is already working on this.
Since Sep 6, 2022.
- Dominant language
- Rust
- Stars
- 70
- Forks
- 16
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 30
Description
Janus aggregators are configured with an HPKE configuration and a private key so that they can vend HpkeConfig to clients and then decrypt uploaded messages. These values are provided either via config file or environment variable as hex-encoded byte strings. At startup, we should verify that a test message encrypted to the aggregator's public key can be decrypted by the aggregator's private key, using the KEM, KDF and AEAD in the aggregator's HPKE config.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.