Make ui-keyring storage-agnostic
See original GitHub issueui-keyring is just a wrapper around @polkadot/keyring
which stores symmetrically-encrypted keys in localStorage. This can only work in web environment.
I’d propose to make it storage-agnostic, and create separately several transports:
- localStorage (for when security is not important, e.g. testnets)
- AsyncStorage (for React Native)
- file system (if used in node.js)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Create a key ring | Cloud KMS Documentation - Google Cloud
Create a key ring. ... Build the parent location name. LocationName locationName = new LocationName(projectId, ... CreateKeyRing(locationName, id, keyRing);
Read more >Keeper's Commitment to Staying Platform Agnostic
Automatically generate unique, high-strength, random passwords for all your sites and apps, and store them in a personal, encrypted digital ...
Read more >Repositories | Documentation | Poetry - Python dependency ...
In the above example, the credential will be stored using the name poetry-repository-pypi . If access to keyring fails or is unsupported, this...
Read more >Apple AirTags vs Tile tracker | CNN Underscored
Tile has a network made up of millions of devices, while Apple uses its ... (or who prefer an agnostic OS approach) should...
Read more >Apple Platform Security
up with dramatic changes in a user's facial hair or makeup use while ... (IKEv2/IPsec only) The keys are stored in the System...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, there needs to be a different solution so you cannot “muck about” with the observable. apps also uses the observable directly, but just to “observe”, so
subscribe
and done.Additions to FileStore is welcome, not sure it works. (But started typing and couldn’t stop.) The repo, as the name suggests, really is specific to the browser, and Electron is a browser as well. It is not too much of an issue to include that one in here since it basically needs fs, mkdirp - which generally is needed in other places as well for Node. So it shouldn’t break any real webpack-like env.
The issue with all these is that the footprint is so small that a package for the single handful of lines is just absolute complete overkill. However, the big drawback is that extra deps can be pulled-in. (i.e. every user now all of a sudden has a dep on
extensionizer
, and well,store
as the default store.)This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.