-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add APIs for encoding and decoding key configs for wire transmission #8
Conversation
@dajiaji it's not clear to me why the Node.js test is failing -- do you happen to know? |
@chris-wood Could you update your dnt library in import-map.json to the latest (v0.33.1) and try again? |
@dajiaji thanks -- that seemed to yield a different error now! Please see below when you have a moment:
|
@chris-wood It seems to be due to the fact that dnt's npm support is not complete. Could you apply the following change to dnt.ts?
|
@dajiaji that did it -- thank you! 🙏 |
No problem. Sorry to bother you with deno-specific problems. |
kem: kemId, | ||
kdf: Kdf.HkdfSha256, // Garbage (to create the suite) | ||
aead: Aead.Aes128Gcm, // Garbage (to create the suite) | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems to me that it would be better to make hpke-js disclose the KEM classes directly.
Closes #7.
This lets applications transfer the key config over the wire from gateway to client.