Keepass2Android & ownCloud are playing with each other again

tl;dr: All is well with the world once again. :-)

A while back, I switched from LastPass to KeePass for password management; while I had no suspicion that my passwords were compromised with LastPass (they’re stored in such a way that they’re not supposed to be able to read them), I still felt better having my password info residing on equipment under my control.  (That KeePass is also open-source is a nice bonus.)

My password database is in a WebDAV share served up by an ownCloud instance on a server at home.  This makes it accessible from pretty much anywhere: home, work, on-the-go.  KeePass provides a desktop client that runs anywhere you can get either the .NET Framework or Mono running, so both Windows & Linux are covered.  For Android, there’s Keepass2Android.

For the past few months, though, there’s been a snag.  There was an ownCloud upgrade that kept Keepass2Android from being able to access the password file over WebDAV.  (It also broke WebDAV access for a bunch of other Android apps; I think the only one that still worked was ES File Explorer.)  Trying to load the password file directly from WebDAV would throw an error.  My workaround was to grab it with ES File Explorer, note the location, and have Keepass2Android load the local copy.  This, however, breaks synchronization between devices.

I don’t know if ownCloud changed or if Keepass2Android changed, but as of the versions I’m currently running (ownCloud 8.0.2 and Keepass2Android 0.9.7), loading the password database over WebDAV works again.  This means a password created or changed on my phone or tablet gets synced back to the server so that it appears across all my devices (including desktops and notebooks).