I'm using KeePass on regular base and also use File-Attachments (smaller essential files like private/public keys, and so on). In sum my Keepass KDBX is now 52 MB and takes very long for loading/saving using ftp sync (on my remote server with backup on it).
I think mostly this is because the file-attachments sum up to this large file. Wouldn't it be a handy feature to store such files separately? f.e. we could create a folder [KeePassDB-FileName].storage and put files in there and use same encryption/key like main-db for these files. The KeePassDB-File attachment should then work like a "reference" to this file which may lead to a new KeePassDB-Version implementing this feature.
Could such a feature be implemented using a plugin (cross platform linux/osx/windows) or is it required to touch KeePass-DB Format for implementing Attachment-References? To keep in mind... the references should always work with BaseURL/Base-Path to the KDBX-Filename and ".storage/attachment-hash" so that it doesn't matter the file has been loaded "locally" or using ftp/scp and so on.
Please leave some feedback. Anyone interested, too? Anyone who is able to develop such thing?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Having more than one database file is asking for trouble IMO.
KeePass stores the attachments internally, including old attachments as part of the history. Try deleting individual history items, or use Tools > Database Tools > Database Maintenance, to clean up old history items.
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using KeePass on regular base and also use File-Attachments (smaller essential files like private/public keys, and so on). In sum my Keepass KDBX is now 52 MB and takes very long for loading/saving using ftp sync (on my remote server with backup on it).
I think mostly this is because the file-attachments sum up to this large file. Wouldn't it be a handy feature to store such files separately? f.e. we could create a folder [KeePassDB-FileName].storage and put files in there and use same encryption/key like main-db for these files. The KeePassDB-File attachment should then work like a "reference" to this file which may lead to a new KeePassDB-Version implementing this feature.
Could such a feature be implemented using a plugin (cross platform linux/osx/windows) or is it required to touch KeePass-DB Format for implementing Attachment-References? To keep in mind... the references should always work with BaseURL/Base-Path to the KDBX-Filename and ".storage/attachment-hash" so that it doesn't matter the file has been loaded "locally" or using ftp/scp and so on.
Please leave some feedback. Anyone interested, too? Anyone who is able to develop such thing?
Having more than one database file is asking for trouble IMO.
KeePass stores the attachments internally, including old attachments as part of the history. Try deleting individual history items, or use Tools > Database Tools > Database Maintenance, to clean up old history items.
cheers, Paul