Replies: 1 comment
-
secretbox is available natively crypto_box, others etc (combining x25519) are available in noble-sodium wrapper around noble cryptography: https://github.com/serenity-kit/noble-sodium |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I see this quote on the README:
A couple of questions:
Sodium uses the term "secretbox" (
crypto_secretbox_easy(..)
andcrypto_secretbox_easy_open(..)
) for its symmetric authenticated encryption (same key for encryption/decryption). Further, they use the term "box" (crypto_box_easy(..)
andcrypto_box_easy_open(..)
) for their asymmetric authenticated encryption (by generating an ephemeral keypair).But they use "sealedbox" (
crypto_seal(..)
andcrypto_seal_open(..)
) terminology for its un-authenticated (anonymous) asymmetric encryption/decryption.Do you support (have aliases for) all three of these: "secretbox", "box", and "sealedbox"? Or only some of them?
Where specifically on the noble-ciphers API are these various "seal / open method" aliases located? I couldn't find them.
My desired goal is to do the "sealedbox" equivalent with Noble, from this Sodium-using code:
I'm trying to figure out if these aliases already exist, or if the pieces are there in Noble (Ciphers, etc) to do the equivalent operations, specifically where values would be interchangeable between a Sodium-using implementation and a Noble-using implementation.
Any thoughts/tips/guidance are appreciated.
Beta Was this translation helpful? Give feedback.
All reactions