4 ms·
Assume it is a NodeJS Electron app that people run locally (and in the future, a browser extension). (there is also a web version, which of course could always
by marknadal 9y ago
Assume it is a NodeJS Electron app that people run locally (and in the future, a browser extension).
(there is also a web version, which of course could always be compromised, but we're encouraging users to download the app so they have full control and don't have to worry about that. But they need to be compatible.)
Telling our users not to use crypto isn't an option. Recommending our users not use a browser is possible, but forcing them not to use a browser isn't an option either.
- lvh 9y agoI don't think you can do this safely without having a security person on board. And there's a chance they'll try to ship a real crypto library in the Electron app. I'll give it a shot though, some things that come to mind: * RFC6979 ECDSA or bust * Have you considered off-curve attacks for that ECDH? * How do you authenticate your symmetric ctexts?