hasch2k08

I've been using the webdav synchronisation for a while now and since my cloud provider changed its URL I had to set up the webdav sync on all my devices all over again. While doing that I noticed that Enpass on macOS always creates an additional subfolder called "Enpass" even if the webdav path already contains the word "Enpass". My android phone, Linux machines, windows machines, my iPad do not have the problem only Enpass on my MacBook air Early 2014 with macOS Big Sur does. What is the problem in detail: My webdav path used to be "https://mycloudProviderName.com/webdav/Enpass". In my cloud storage I've used to store my Enpass vault in a separate folder called "Enpass". That's why the webdav path contained the word "Enpass". All my devices mentioned above store or sync my Enpass vault in the path "https://mycloudProviderName.com/webdav/Enpass/vault.enpassdbsync ". But not my MacBook air, Enpass on this machine stored the Enpass vault in "https://mycloudProviderName.com/webdav/Enpass/Enpass/vault.enpassdbsync". Which either meant that I had two different vaults stored in my cloud or one of my devices could not find the existing vault since the devices use different path in the cloud storage. The work-around which works, but not as expected: After I've understood the problem I've changed the folder structure in my cloud storage to "https://mycloudProviderName.com/webdav/Test123". Now the synchronisation between all the devices works just fine. But the data is stored in "https://mycloudProviderName.com/webdav/Test123/Enpass/vault.enpassdbsync". The additional subfolder "Enpass" which is now created or presumed, depending if the device creates the vault in the first place or just syncs with it, is used on all devices and not just on my MacBook. "Not great, not terrible" as Anatoli Djatlow would say (May god rest the soul of Paul Ritter). Conclusions: It seems to me that the urge to create a new subfolder called "Enpass" when syncing using webdav is in all Enpass apps on all operating systems. Unfortunately, only on macOS the Enpass app does not notice that Enpass is already in the provided webdav path. If you ask me Enpass should not create a subfolder for itself at all or at least not without asking. I've been using Enpass for almost three years now and since I've been using webdav synchronisation from the beginning this bug must have been introduced after the February of 2019 or it is caused by one of the countless updates of macOS since then.

I am really sorry that I did not explain this properly. What I meant was, that you have to delete your password history in Keepass before you make the export to the XML file. I think the problem is that the Enpass XML Parser or the import in general has a problem if the XML File contains any form of password/login history. I came to this conclusion because I recognized that after the crash Enpass has imported some of my passwords. I tried several times and the result kept the same, every time the same passwords were imported. So I assumed that a particular login/entry caused the crash. I analysed the Keepass Export XML file, deleted and altered some entries and came to the conclusion that any form of history for an entry caused Enpass to crash during the import of the XML file. Fortunately Keepass has the feature to delete the history of entries. Some of you might need this history, but for me it was not necessary and so this workaround worked perfectly fine for me.

I have the same issue with Keepass 2 XML Export and using Windows 7 as well as using MacOS Mojave. Fortunately I could develop a workaround: Delete the history of all your entries and the import will work. It seems to me that the Enpass Import somehow crashes on every entry when the database export contains a non empty <history> section.