You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my scenario, KeePass with KeeChallange is used with Windows 10 und Ubuntu Linux. Files from both systems are synchronized, using owncloud.
When opening the KeePass file under Windows, the KeePass.xml (that belongs to KeePass.kdbx) is sometimes rewritten (probably if I save changes?). The new filename is KEEPASS.XML, showing Windows' ignorance for filename case sensitivity. As soon as I try to open my KeePass file, I am shown a message that my KEEPASS.XML is invalid, and I should use the fallback method.
Fortunately, owncloud allows me to change the XML file back to it's last version (which was saved under Linux), and then everything works fine. However, it would be easier if the Linux version of KeeChallange could just handle the Windows files. As the Windows XML file is slightly larger, I assume, it's possibly just a matter of newline characters...
The text was updated successfully, but these errors were encountered:
In my scenario, KeePass with KeeChallange is used with Windows 10 und Ubuntu Linux. Files from both systems are synchronized, using owncloud.
When opening the KeePass file under Windows, the KeePass.xml (that belongs to KeePass.kdbx) is sometimes rewritten (probably if I save changes?). The new filename is KEEPASS.XML, showing Windows' ignorance for filename case sensitivity. As soon as I try to open my KeePass file, I am shown a message that my KEEPASS.XML is invalid, and I should use the fallback method.
Fortunately, owncloud allows me to change the XML file back to it's last version (which was saved under Linux), and then everything works fine. However, it would be easier if the Linux version of KeeChallange could just handle the Windows files. As the Windows XML file is slightly larger, I assume, it's possibly just a matter of newline characters...
The text was updated successfully, but these errors were encountered: