3 ms·
One interesting option would be to bring this kind of P2P syncing to KeePass. This would benefit from all the features that are already build into KeePass.
by jpalomaki 13y ago
One interesting option would be to bring this kind of P2P syncing to KeePass. This would benefit from all the features that are already build into KeePass.
- geertj 13y agoWhy not improve something existing is a valid question, and I did look into it. The difficulty is that a P2P sync requires a completely difference design. Keepass is pretty much a frontend to an embedded database. A P2P node need to have its own network facing component that acts independently of the frontend, to relay messages, respond to pairing requests, etc. This is why Bluepass has a frontend/backend architecture. It is a lot easier to create such a different architecture from scratch.
- reedlaw 13y agoIMHO KeePass is in need of a reboot. First, it's very confusing which version to use. KeePass 1.x (Classic), KeePass 2.x (Professional), or KeePassX (originally KeePass/L for Linux?). When I first tried them out, I settled on KeePass2 because it supported filling out browser forms in Linux. But it's a mono app with an ugly interface. With no built-in syncing support and no good syncing plugins either. I hope this project can become a suitable replacement.