Ouch. 1Password is probably the best usable password manager today; they can do better in a few areas, including this. Another area would be putting blessing/device keys on each device on top of a password, because I don't trust a passphrase alone, and many platforms are getting trusted computing features -- you have a slow process to put a device key on each thing, which is then entangled with your passphrase to decrypt. You could even do a hw token, too. Another area they could improve is network sync -- I don't trust iCloud or Dropbox, and wifi-sync is a pain, so supporting WebDAV or some other open format they could develop would be a lot better.<p>Long tangential digression:<p>My personal design goal is to maximize the number of distinct entities which have to collude to cause me serious harm.<p>Pure online SaaS is often very bad. There are cases where the risk is acceptable, but "here, maintain a password list" is not one of them. The "shared google sheet full of password" is a great example of this. Evernote is another example. I avoid these wherever possible.<p>Systems like LastPass where the binary is distributed by an entity every time I use it, and then talks to that same entity for the backend, are are better, but still bad. Hushmail was the canonical honeypot of this type -- download a java applet after logging in...<p>A long-lived binary (standard client software) talking to servers operated by that entity is better. Swapping the binary out is more detectable, and harder to do for a single user. iOS apps are probably the best for this right now, since Apple is sort of a semi-trusted intermediary here. You'd at least have a shot of catching the compromise after the fact.<p>Client software which talks to servers run by separate third parties is better. e.g. 1P using iCloud/Dropbox. It is better as the set of third parties is bigger and more diverse.<p>The ideal is being able to run client/server on your own platforms. Being able to run a cloud storage service (e.g. AeroFS) entirely on your own private network is ideal.<p>Open source on top of this is great, but in reality independence of operating the services is worth more. An open standard with multiple implementations, many of which are open source, would be meaningful, but merely publishing source code isn't as meaningful, at least without verifiable/repeatable builds and a good runtime level matching.