You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working with the Secure Scuttlebutt protocol which makes heavy use of many high-level libsodium APIs. I noticed that this package is not exposing sealed and secret boxes and other features from that library.
I don't know if the maintainers of this package are interested in such features or if I should work on creating a separate sodium package. I decided to check here if a PR for such features is OK before I start coding anything.
The text was updated successfully, but these errors were encountered:
Thanks for the message. Yes, I would be happy with adding support for libsodium APIs.
I glanced over the page you linked to, and the missing features that I noticed were sealed boxes, secret boxes, and conversion from ed25519 (signing) keys to curve25519 (DH) keys. Are there any others needed?
Here are my thoughts on implementation:
The sealed box operations can be added as methods of sodium-x25519-key%.
Conversion of ed25519 keys to curve25519 keys can be done with a method on sodium-ed25519-key%.
The secretbox construction is like a cipher (but not a full AEAD cipher, sadly, since it doesn't allow additionally authenticated data).
I've created a branch b-sodium-api with a partial implementation.
Hi,
I'm working with the Secure Scuttlebutt protocol which makes heavy use of many high-level libsodium APIs. I noticed that this package is not exposing sealed and secret boxes and other features from that library.
I don't know if the maintainers of this package are interested in such features or if I should work on creating a separate sodium package. I decided to check here if a PR for such features is OK before I start coding anything.
The text was updated successfully, but these errors were encountered: