search

subdavis / Tusk

🐘 🔒 KeePass-compatible browser extension for filling passwords.
https://subdavis.com/Tusk
Other
482 stars 74 forks source link

webdav database is not refreshed ? #205

Open bonjour81 opened 6 years ago

bonjour81 commented 6 years ago

This issue is a

Please describe the current behavior, and explain why it's bad.

Hello ! following issue #133 and also because I currently try to get rid à google, I test webdav. I opened a free small cloud drive on drivincloud with only my keepass database. Tusk can connect and find the file, no troubles. Then I use keepass2android app for password management on my phone, but also to create new passwords. It's convenient & does not need to install keepass (not possible everywhere).

When I used gdrive: I can create a new password on my phone, sync the database on gdrive with keepass2android, open it with tusk immediatly and find my fresh long & complex new password and I can use it for example to finish registering on a new forum or whatever.

Now, with webdav, it looks like tusk does not "refresh" the updated file. it seems to re-open it like usual, and I can still access my older passwords, but cannot find the new one. The database is well updated on the drive by keepass2android: if I download it and use it with tusk as a local file, I find the new password. If I play around and then switch back tusk to webdav, it can now find my new password.

Let me know if any further tests can help ?

subdavis commented 6 years ago

Thanks for opening this issue. Might be an overzealous caching problem. WebDAV should absolutely update automatically. I'll have to investigate with driveincloud and check back with you.

bonjour81 commented 6 years ago

Thanks ! DrivinCloud is a french website. if you like to open an account or whatever and need help, let me know. I'm not sure it make any difference, but just in case: keepass2android is connected to this drive through SFTP (just because I wanted to try this protocol, keepass2android could handle webdav too).

Best regards,

bonjour81 commented 5 years ago

Hi ! I would like to add a few element to this issue. Today, I changed my database by adding a keyfile in addition to password (keyfile + password needed to open). What ever I tried: -locking / reopening databse -remove webdav server and adding again -renaming database -deleting everything in tusk / advanced parameters -rebooting

it keeps opening again & again I assume a cached database (I added a dummy key in the database which is still not visible from tusk) and it does unlock without keyfile.

Accessing webdav by directly pasting webdav link in firefox address bar does show that the file was updated. downloading the file from here and opening it with tusk as local is working fine: it does ask for keyfile and does show the dummy entry.

Is there any chance that, for some reason, tusk does not re download the file ?

How can I investigate further?

subdavis commented 5 years ago

So you've got two files in your webdav store. Let's call them old.kdbx and new.kdbx.

Are you saying they both open without a keyfile? You can switch databases in tusk and they both show up right?

bonjour81 commented 5 years ago

Hi! not exactly. I renamed my older database (without keyfile) to database.old (not kdbx extension). Then, I uploaded my new database.kdbx, requesting keyfile, with same name and location as previous one: I was expecting this to be kind of plug&play :) for Tusk and keepass2android that I use too.

Only the kdbx files seems to be found by tusk in "manage database" (the .old file is not displayed)

Finally, all the tests I mentionned before, I renamed database.kdbx to database2.kdbx: the filename was correctly scanned and detected in "manage database" but still not asking for keyfile. After a while, I notice that in the popup menu (when clicking Tusk icon in firefox toolbar), it was still trying to open database.kdbx. So I clicked on "change" and was able to select database2.kdbx (now requesting keyfile).

I'm still confused on how I was able to open my old database (or I assume a cached copy of) while it was renamed on the server?

rtcunningham1 commented 5 years ago

I can confirm the WebDAV behavior. I updated a password with KeeWeb and then tried to use that password with Tusk. Tusk would only offer the old password. I checked the database using KeeWeb and then KeePassX and both showed the new one.

I did everything up to removing the extension and reinstalling it. The only thing that worked was copying the database and switching to it with the extension.

Other than this bug, Tusk works perfectly.