Only sender pubkey in hpke.base metadata seal #116
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refs #86 (comment)
Description
Changes to benchmarking code:
Envelope(the message payload to the server) per followup discussion with ethz - no need to double-encrypt them. (This matches the manuscript).It theoretically means that there should be a wrapper type for the ciphertext in the Envelope (to keep with theedit: there's a wrapper type. :)C, X, Zformat), but since it's a quick benchmark implementation I have left all the bytes as separate types rather than concatenating them and them parsing them.CombinedCiphertexttype for serializing/deserializing all the parts, but I kept the type signature and even variable name in theEnvelopestruct unchanged, to avoid having to make any wasm-bindgen changes).Test plan
make bench