Kyrodan
Google Drive (restricted) doesn't work with Yubikey
Describe the bug As many others I had to change to "Google Drive (restricted)" after Google changed something on their side and invalidated my previous acces token.
I have as a second factor for the KeePass DB whic is a YubiKey. Unfortunately this doesn't work any more because the new way of accessing the Google Drive files prevent KeeAnywhere plugin from reading the XML file which accompanies the KDBX file.
To Reproduce Steps to reproduce the behavior:
- Manually download KDBX and XML file from Google Drive to local folder
- Open KDBX file
- Enter Master password and choose 2FA provider "Yubikey challenge-response", click OK, touch Yubikey, the password DB opens.
- File => Save As => Save to Cloud Drive => Choose previously setup Google Drive account, choose filename, click OK
- Only the KDBX file gets saved. The XML file is missing on the Google Drive root directory.
- When manually placing the XML file there the KeeAnywhere plugin can't read it when opening the KDBX from Google Drive. It gives error "Error: file gdrive-r///Username/PasswordDB.xml could not be read correctly. Is the file corrupt? Reverting to recovery mode"
Expected behavior KeeAnywhere should save both, KDBX and XML file to Google Drive
Screenshots None
Environment:
- OS and Version: Windows 10 22H2
- KeePass-Version: 2.57.1 (64-bit)
- KeeAnywhere-Version: 2.1
Additional context This worked in the past when KeeAnywhere was able to read any file in my KeePass folder on Google Drive
I don't have one of these devices to test with, but one thing I can think of to check: make sure your xml file does not already exist in the root of your drive before you press save as in step 4.
I have the same problem. Since switching to gdrive restricted the necessary xml file is not saved in google drive. I cleaned the "root" folder of google drive - so no xml file there. Using dropbox (not restricted mode) saves the xml file - but fails at opening the database in the same way.
