-
Could Hybrid Public Key Encryption (HPKE) [[RFC9180](https://www.rfc-editor.org/rfc/rfc9180)] API design be included? Single-Shot for sure, possibly Multi-Shot too?
panva updated
1 month ago
-
### Description
eg see https://datatracker.ietf.org/doc/rfc9180/referencedby/
It would be nice if the title changed from "References to rfc9180" to "XXX References to rfc9180"
### Code of Conduct…
-
When a KEM keypair is derived in liboqs, it relies on randomness using [rand.h](https://github.com/open-quantum-safe/liboqs/blob/main/src/common/rand/rand.h). In some situations, it's useful to genera…
-
The spec for HPKE states that the private key size (Nsk) for DHKEM(P-521, HKDF-SHA512) is 66 bytes:
https://datatracker.ietf.org/doc/html/rfc9180#name-key-encapsulation-mechanism
The private key '…
-
Daisuke wrote:
> At the very least, until now, I believed that the `info` value for HPKE should be an empty string. The reason is that HPKE interface used in COSE is essentially the Single-shot API…
-
@hannestschofenig @selfissued @OR13 and other folks,
I think Orie also mentioned this in another issur/PR, but how about providing test vectors in the COSE-HPKE spec?
Since the COSE specs are re…
-
We need to determine if we are comfortable that the current language regarding how the client facing server and the backend server interact is clear enough.
If not we need to bring it to TLS worki…
-
Right now, we're a little imprecise when we talk about how the encryption of various pieces is put in place.
Each match key is protected toward the three helpers. There is not a lot we can do to o…
-
### Describe the issue
https://datatracker.ietf.org/doc/html/rfc9180 includes a lot of inline code blocks (like [this one in Section 5.1.1](https://datatracker.ietf.org/doc/html/rfc9180#section-5.1.1…
-
hi! I'm wondering if there was some plan (or something already available) for adding functions for long-term asymmetric encryption?
I see the KEX module but it's explicitly documented as for single-s…