-
Notifications
You must be signed in to change notification settings - Fork 193
plugins: expose native crypto library #1488
Comments
Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on. If no reviewer appears after a week, a reminder will be sent out. |
This will need investigating I think. I want to prevent things such as making the OS unresponsive due to intensive hashing which uses up all the machine's resources |
This issue or pull request needs further investigation. Please wait for further information, thank you. |
|
Will be addressed in the 3.0 release. |
This issue has been closed. If you wish to re-open it please provide additional information. |
It would be very useful if the native
crypto
library could be exposed in the plugins sandbox.One particular use case is that it would allow plugins to generate HMAC access tokens which are required for many external APIs. I think the library is safe enough to not require any permissions and all its functions could be exposed e.g. via
walletApi.crypto
since none of them appear to be potentially nefarious and all have legitimate use cases within plugins.The text was updated successfully, but these errors were encountered: