Re-export HPKE for `enclave_encrypt:: EnclaveEncryptClient` users
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 41
- Forks
- 25
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 15
Description
When instantiating EnclaveEncryptClient users need to reach into HPKE because from_enclave_auth_key_and_target_key requires hpke::Kem:
https://github.com/tkhq/rust-sdk/blob/bbd8ea76d3ae09a7b37cdf388ec894cecde98ef9/enclave_encrypt/src/client.rs#L308-L318
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.
Research direction
Start in enclave_encrypt/src/client.rs around lines 308-318, where from_enclave_auth_key_and_target_key requires hpke::Kem. Re-export the needed HPKE API so enclave_encrypt::EnclaveEncryptClient users do not need to reach into HPKE directly; done means that construction can use the required type through the client crate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100