Open dougbebber opened 4 years ago
For reference, here are some links to a similar request in the Scatter Desktop repo:
https://github.com/GetScatter/ScatterWebExtension/issues/39 https://github.com/GetScatter/ScatterDesktop/issues/43
pull request: https://github.com/GetScatter/ScatterDesktop/pull/141
ScatterJS and Scatter 12.1.1 now supports shared secret generation for EOSIO blockchains.
https://github.com/GetScatter/scatter-js/blob/master/mock-sites/eosjs2/index.html#L293
Our Dapp deals with sensitive user information and we would like to encrypt/decrypt text that flows from our Dapp (client) to our smart contract actions.
We would like to perform the symmetric encryption ourselves inside our Dapp. However, for security purposes, we would like to rely on a signature provider (EOSIO wallet) to support a shared secret (client and smart contract account) approach to obtaining an encryption key (derived from EOSIO keys) and a nonce, to use say for an AES password.
Similar functionality used in Scatter Desktop can be found at: https://github.com/GetScatter/ScatterDesktop/blob/encrypt_keys/src/util/Crypto.js
I'd like to see similar functionality in the eosio-signing-request standard to enable the transmission of sensitive data on EOSIO chains.