Greatly improved security by splitting the password db
Safe in cloud actually sync with public cloud services.
In case of breach, we're told the db is impossible to break because of AES.
We can do even more by making the security virtually impossible to break :
the user could choose the different cloud storage to use, ie Dropbox and OneDrive or Dropbox + OneDrive + Google Drive or whatever
the password db is splitted and then synced
An unencrupted example : let's say we have the content "123456". The user selected Dropbox and OneDrive for sync.
This content would not be synced with "123" for Dropbox, "456" for OneDrive but everything would have been mixed before sync.
This means a definition is needed to unmix this. This definition could be sync as a file to Google Drive for example. The definition file is unaware of where are the mixed files are as it is just a defeinition to unmix.
It's dividing to conquer, so even if whatever Dropbox or OneDrive or Google Drive storage area is accessed, really no one (even the cloud storage owners or rsa) can do a thing to stole your data even if there is an unknown breach in AES or whatever.
The sync is heavier but security is dramatically improved which should satisfy even paranoid guys. It would be even better securized than services such as lastpass, dashlane etc... and a better security layer than two-factor authentification used in these services.
Alexandre Emeriau commented
Think of the news where you see authorities asking for having the keys to uncrypt your data.... in this scenario, you could give them the key, whatever they won't be able to do anything with it...
I participated in suggested owncloud support, that mean we would have a private space whereever on the net hosting a part of our db, this is even a nightware for anyone wanting to steal your data. You can even improve by switching on and off owncloud whenever you want instead of being always online...so i guess this would put a shutdown to initiative to steal your data.