fix: persist auth state in electron storage #182
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We need to store our auth and refresh token somewhere else than in local storage. We temporarily put it there because the safe storage prompt was annoying in dev.
This PR makes its so it's instead stored encrypted in application support in
renderer-store.json.The encryption key is derived from node-machine-id which returns a stable hardware UUID.
Format is like so.
If someone has file access on your machine, they can derive the same key. But if an attacker has that level of access, the user has bigger problems. The encryption primarily prevents token theft via cloud sync/backups/similar cases.