Open jversusk opened 2 years ago
You aren't hiding anything by having a different extension for your database. How do you think we detect it is a kdbx database without the extension being correct? There are two "magic" numbers at the start of the file that identify it. Any program can use those to find the databases in your files 😉
I do agree we will remove the extension check for keeshare eventually.
The idea isn't to hide it from programs, but to not make it obvious to a person 😁
I prefer to save databases with a different extension, so it's not easily identifiable as a KeePass database. While KeePassXC allows opening and saving of databases with any extension, the KeeShare (Synchronize) feature insists on a .kdbx extension. This is an unnecessary requirement and inconsistent with the open/save behavior.
Steps to Reproduce
Expected Behavior
The Path file extension shouldn't matter as long as the container is of the correct type.
Actual Behavior
The following error appears:
Context
I suggest making the KeeShare behavior consistent with the open/save behavior, by removing the .kdbx extension requirement.
Environment
KeePassXC - 2.4.3 Operating System: Linux