[Feature Request] export sigma32_32 from _arx.ts or simply the constant 'expand 32-byte k' that it's derived from about noble-ciphers HOT 6 CLOSED

0.5.3

from noble-ciphers.

5bce492

from noble-ciphers.

as for secretstream - i don't think it's very popular, but documenting a way to encrypt huge files would be useful for README.

from noble-ciphers.

Quick turnaround dude, thanks!

And you're right about secretstream, only discovered it not too long ago. The motivation was less about huge files and more about configurable chunking to counteract the limitations of the stream cipher, although that's definitely a plus.

But I'll hopefully be able to get around to an implementation of it using noble for an entry in the readme. Will keep you posted 🙏🏽 thanks again for that quick release

from noble-ciphers.

@paulmillr not sure how esbuild didn't pick this up before, but _arx isn't set in the package exports...

The path "./_arx" is not exported by package "@noble/ciphers":

    node_modules/@noble/ciphers/package.json:35:13:
      35 │   "exports": {
         ╵              ^

  You can mark the path "@noble/ciphers/_arx" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle.

Not sure you're too keen on exposing too much to the public api, seeing as though the file's marked as pseudo private with the _ prefix.

But on the other hand it would expose the internal createCipher method to enable more customised usage.

Or could just re-export from the utils export, maybe aliased to not cause confusion.

Either way is fine with me, but depends what you think is best.

If neither option is good it's fine I can just switch back to constant, seeing as though it literally is just a constant.. guess it was just a QOL improvement.

LMK your thoughts

from noble-ciphers.

«But on the other hand it would expose the internal createCipher method to enable more customised usage»

what’s the use case?

from noble-ciphers.