-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Secure storage for "secrets"? (LCP SHA256 passphrases, OAuth access tokens) #900
Comments
Important: on MacOS KeyChain, user-level access control is actually based on any NodeJS executable (i.e. not bound / tied specifically to Thorium), so the protection is actually relatively easy to circumvent once an attacker gains access to a user computer, to steal passphrases and access tokens (it would be harder than simply copy/pasting the DB contents from semantic-release/cli#256 atom/node-keytar#88 |
As mentioned above, KeyTar offers a little bit more obfuscation but the protection can be broken, and the cost of compiling the native lib + potential bugs (as experienced with LevelDown for example) are a bit off-putting. |
"any node.js process later on can access it without prompting the user. (When you package your Electron app, this value will be your app’s name and only your app will have access without prompting)." |
Native Electron alternative to |
Currently, Thorium stores this information in the database.
Possible technical solution?
https://github.com/atom/node-keytar
=> note that just as with LevelDown, KeyTar would need to be recompiled against the current Electron / NodeJS version used by Thorium (npm
postinstall
)The text was updated successfully, but these errors were encountered: