Dave Longley
Dave Longley
> Can you please point what am I doing wrong? No, unfortunately! Everything worked for me ... let me show you what I did. I generated a fresh keypair: ```...
Btw, if you run it with the defaults in forge: ```js const t = privateKey.decrypt(forge.util.decode64(y), 'RSA-OAEP'); ``` It also works.
To help you guys figure out what's going on here, we need to be able to replicate the issue. Do you have example private keys (please generate new throwaway ones)...
@davidlehn, can this be closed? I think we use webpack 5 on the main branch now.
Oh, no, just kidding, looks like we still haven't switched to webpack 5.
Unfortunately, we have not yet implemented a SubjectPublicKeyInfo/X.509 representation of ed25519 public keys. PRs are welcome!
The ed25519 internals all use Float64Arrays for consistency and to ensure there are a sufficient number of bits. For more discussion, see: https://github.com/dchest/tweetnacl-js/issues/45
Some of the docs in here make it seem like the functions are specific to node.js buffers, etc. -- when they aren't. The docs can mention that if you're using...
I don't know what the status is, but so we can better track it I'm linking to that other PR: #697.
We've got some partial TLS 1.2 work done on the 0.8.x branch, for example [this](https://github.com/digitalbazaar/forge/commit/7b60b2a06c2123868faff9942f34ed58105a8149). We'll need to figure out what's in common and merge things.