Show HN: CryptexVault – Decentralized Password Manager https://ift.tt/JAivYq3

Show HN: CryptexVault – Decentralized Password Manager https://ift.tt/JAivYq3

Show HN: CryptexVault – Decentralized Password Manager Hi everyone! We started working on this project last year because a password manager that we used was being sold to another company and stopped offering their service. We were not happy with the alternatives that were available so we decided to give it a shot and build our own. We are now at a point where we have a working Beta and are looking for some feedback from the community. The main idea is to have data synchronization without a central server (single point of failure). When you create a Vault (inside which you can store your credentials and other sensitive data), you can "Link" it to other devices. By linking it to other devices, you can synchronize the data between them. - The Vault itself never leaves your device, it is encrypted and decrypted locally, and is only shared with the other devices that you link it to. The data synchronization is done using WebRTC, meaning, the data is transferred directly between the devices without going through a central server . If the devices cannot connect directly, the data is transferred through a TURN server (which is a server that is used to relay the data between the devices). - We are working on a way to allow the users to use their own TURN server (or a TURN server that they trust) or perhaps not use one at all, instead of using the one that we provide. Now, the only problem is how do your devices find each other - Using a signaling server. - We provide a signaling server that is used by default, but we're also working on a way to allow the users to use their own signaling server. In order to allow for easier testing, I've allowed the users to link devices without having to upgrade their account. I would appreciate any feedback you have for us, and if you have any questions, I'll be happy to answer them. Bl4cksmith https://ift.tt/gNUY12L August 21, 2023 at 10:23AM

0 Comments: