Dev crypto done correctly?: check source code. Used publicly used crypto packages too.

Centralised password manager servers vs “dedicated vm” I suppose you mean relay?: 2 layer of encryption, even if their entire VM is hacked, there’s no way to decrypt the data.

Replace you password manager?: it’s your choice, currently all if not all stored and controlled centrally, they can change policy, change billing, change anything they want. Here, it’s running on open protocol.

Reply to this note

Please Login to reply.

Discussion

"Dev crypto done correctly?: check source code. Used publicly used crypto packages too."

Libbitcoin could have said the same thing. Anyone could have checked their source code, but now we have https://milksad.info.

"Centralised password manager servers vs “dedicated vm” I suppose you mean relay?: 2 layer of encryption, even if their entire VM is hacked, there’s no way to decrypt the data."

What are you smoking? I mean a dedicated vault virtual machine with no internet. Preferably on Qubes OS.

"Replace you password manager?: it’s your choice, currently all if not all stored and controlled centrally, they can change policy, change billing, change anything they want. Here, it’s running on open protocol."

WTF? My keepassx open source software cannot do any of that without me accepting by installing and running that version.