Bl4cksmith
Joined 4 years ago
Joined 4 years ago
When you save your password on your PC, the password is saved into an encrypted store that is physically on that PC, and to get it to your phone you need to have the application (be it web or native android) open and your vault unlocked so that the two can synchronize.
What I do is to prepare the phone vault by unlocking it and synchronizing right away as I make changes if something is critical.
That is the trade-off when it comes to convenience as compared to something like BitWarden, for example. There the credentials are stored in a centralized database that your PC or phone can reach independently of each other.
EDIT: More details here: https://www.cryptex-vault.com/docs/synchronization
You can follow progress here: https://www.cryptex-vault.com/security
I'd say that the most important part of the infrastructure is the signaling server (websocket server), and the STUN/TURN server used in WebRTC connection forming.
One interesting fact about the currently running application; the application itself is client-side rendered. If you would download the application bundle that you get when you open the application in your browser, you could use it if you would mock networking requests - this would basically simulate the way it works now when the PWA is offline. With the application being client-side rendered - every user gets the same code.
Tell me what you think!
If there's anything you need help with, just let me know - I'll do my best to help in any way I can :)