Operation request: RSA operations

[n1474335]

Summary

Various RSA-related operations could be added. As we are already importing the forge library, it would make sense to utilise it for this.

Possible operations:

• Generate RSA key pair
• RSA sign
• RSA verify
• RSA encrypt
• RSA decrypt

[GCHQ77703]

Started work under the rsa branch, current progress:

• Generate RSA Key Pair
• RSA Sign
• RSA Verify
• RSA Encrypt
• RSA Decrypt

[mattnotmitt]

@GCHQ77703 I assume we're waiting for this to merge? I've tried using your branch but generation isn't working due to a dynamic import of prime.worker.min.js not resolving correctly due to webpack.

EDIT: I've managed to finally make it import with a hacky solution using raw-loader but we still need this PR to merge for self to be an available scope inside the worker.

Another edit: Looks like we've run around into the OperationConfig issue again, which is the actual reason for the self error with the hacky import. A quick explanation of what I'm doing to try and get this to work in this commit. By loading the file as a raw blob we can provide it as a URL for forge to load. This should work, however we cannot actually check this because when OperationConfig is being generated, every file is imported and as such, their imports are also loaded, and as the worker looks like a normal import to node, attempts to load that too. However this won't work because self is not defined in node's scope. Right now the only thing I can think of is using dynamic import when it's added but who knows when that'll be.

[GCHQ77703]

@artemisbot Do these issues not occur in the grunt dev development environment? I was able to seemingly generate RSA keys on a worker thread from just my previous code.

Although I must admit to having never used workers before for anything more than caching, some of the operations were taking 5-10 seconds of time with no degradation of the UI, which implies it is successfully being sent off to another worker thread.

[mattnotmitt]

I tried using your commit on your fork with `grunt dev` and was just getting an error in the webapp about forge's workers not loading.

[GCHQ77703]

My build doesn't seem to note any issues, and my cyber chef instance appears to be functional:

[mattnotmitt]

Ooh, interesting. It worked fine in Chrome/Chromium when I just tested it but doesn't in Firefox which is what I use normally. Wonder what's causing that? (this is on exactly the same dev build and machine)

[GCHQ77703]

Ah, true. Can reproduce the problem in Firefox.

Might indeed need to wait on merging this.

[mattnotmitt]

Looks like digitalbazaar/forge#645 merged, I've just checked and it seems to be working totally fine with the previous branch. Going to clean up the operation and create a PR.

[n1474335]

Thanks for all your work. This has now been implemented and merged in #652