WebDAV Support

Tusk can fetch your keepass databases from a webdav server like OwnCloud or NextCloud.

If you use WebDAV, Tusk will store the login details for your chosen WebDAV server in browser local storage. Implementations vary by browser, but this storage area is always un-encrypted and on-disk. This means that if an attacker has physical access to your computer, they may be able to recover the username and password to your webdav server by scanning the contents of your hard drive.

You can remain safe while using the WebDAV feature by following Best Practices below.

To keep your personal files and other WebDAV data safe, it is highly recommended that you follow these practices when using Tusk with the WebDAV feature.

1. Create a new user on your WebDAV server (called "tusk" or "keepass", for example) with no administrative privileges and do not allow it to access any of your files by default.
2. From your regular account, share only your keepass database file with the new user.
3. In tusk, use only this new user. Do NOT give tusk the login information of your normal account.

If you follow these practices, you will ensure that an attacker could only possibly retrieve your encrypted KeePass database file. Assuming your database is also secured with a strong password, your sensitive data will remain secure.

If you're here, odds are you didn't follow best practices. Go do that first.

I added a webdav account in Tusk, but it didn't locate my keepass file.

Tusk conducts a breadth-first search of your webdav server to find files ending in *.kdbx