Kunzisoft
"No memory to load your entire database" I am locked out although I have the keyfile
I am literally locked out.
Describe the bug
Starting from today I receve this warning when I try to unlock my local database as usually.
To Reproduce
Steps to reproduce the behavior:
- Launch the app
- Select the right key file
- Warning about memory
Expected behavior
Usually I open my database without hassle.
KeePass Database
- Created with: KeepassDX foss
- Version: [e.g. 2] maybe 4 i dont remember
- Location: local in Anemo folder
- File provider
- Size: ~60mb
- Contains attachment: [e.g. Yes] yes
KeePassDX:
- Version: [e.g. 2.5.0.0beta23] 4.0.8 foss Izzy
- Build: [e.g. Free] free
- Language: [e.g. French] EN
Android:
- Device: [e.g. GalaxyS8] OnePlus CPH2399
- Version: [e.g. 8.1] Android 14
Additional context
Add any other context about the problem here.
- Browser for Autofill: [e.g. Chrome version X]
I can open a month old kdbx backup. I lost one month of updates, since that was the more recent.
So the latest database file is corrupted. Gone.
Why?
I don't know but 60mb is relatively large database. If you closed Anemo before the full save was performed, the file may have been partially backed up and therefore corrupted.
Anemo is just a SAF file manager.
It is not really a file manager. It relies on system one.
How to do Anemo to involve Keepass?
I'm just theorizing, I don't know what happened in your case. Maybe it's entirely something else, like an attachment that didn't save properly in the application. But without reproducing the problem I don't know how to solve it.
My first theory is that if you use Anemo and cut the link through SAF by locking access to the storage after a certain period, the kdbx save hasn't had time to take place but this would have to be tested.
How to avoid this in future?
Can you help me to know when a saving is partially made?
I have another theory. But I am not a developer.
When the database is open I cannot make a copy of the database.
Is it right? A same file cannot accessed simultainesly from two apps...
I don't know but 60mb is relatively large database.
@serrq I saw one of your previous post in #1559 where you mentioned your database was 130MB. I don't know what you're storing in your database to make them so large. I've a database with nearly 400entries but the size is less than 100kb (I don't store files or icons). Though you've the option to store files...KeePasss is really not intended for file/disk encryption tool. There are other alternatives specific to file protection e.g. https://cryptomator.org/ , https://veracrypt.fr , https://nuetzlich.net/gocryptfs/ etc. KeePass database is prone to corruption in general when you're using such heavy sized database.
@shuvashish76 You have enlightened me.
Do you suggest to relocate all the files attachments in DroidFS (Android)?
Afterwards I will have to create a new vault in KeepassDX because I cannot understand which files have enlarged so much my vault.
I have all files like 470kb. I have to control more accurately.
KeePass is an excellent option which offers so many free features but to be honest it's a password manager and should be treated as such. For example no harm in storing recovery codes of GitHub as .txt file because of less size (personally I try to avoid storing files, I store them as simple notes (not file) under GitHub entry). If you've to store files then I'd say keep them small and simple if possible e.g. OpenPGP .asc public/secret_keys
Do you suggest to relocate all the files attachments in DroidFS (Android)?
Totally up-to your choice and preference :) I've listed some apps here, they'll be added to "Android FOSS" list
Last off topic.
As gallery vault I prefer Photok. It is written in Kotlin. Safe permissions and practices. 100% offline.
https://f-droid.org/packages/dev.leonlatsch.photok/
@J-Jamet Why dont switch Keepass to CryFS? It is more affordable for heavy data and large database, even in the cloud.
https://www.cryfs.org/
These two tools are not designed for the same purpose. KeePass is designed to manage passwords and authentication systems, to centralize a user's credentials so as to have a single point of entry and unlock numerous services, not to store files. If you want to store files securely, don't use KeePass but tools like the ones you suggest.
I can open a month old kdbx backup. I lost one month of updates, since that was the more recent.
[...]
Why?
Because you don't do daily backups.😔
