i guess because of metadata. an encrypted file has no readable header, which the keepass database file probably has so that keepass knows how it is encrypted.
The Dropbox is just a remote backup container. The backup is automated , gathers files from a few locations, dumps them in an encrypted box and push them to Dropbox once a day. The encryption bit is just for some other files which are not encrypted in their natural state.
Why the need to encrypt on Dropbox? Shouldn’t KeePass be secured enough by itself?
i guess because of metadata. an encrypted file has no readable header, which the keepass database file probably has so that keepass knows how it is encrypted.
KeePass don’t have much beyond a password hash for testing if you entered the right password or not.
still something that would identify it as a keepass database file, no?
The Dropbox is just a remote backup container. The backup is automated , gathers files from a few locations, dumps them in an encrypted box and push them to Dropbox once a day. The encryption bit is just for some other files which are not encrypted in their natural state.