Failed to open S3 remote database with Yubikey Challenge-Response from KeeChallenge plugin

[lcdennison]

I believe there may be some incompatibility between KeeAnywhere and KeeChallenge (a plugin to enable Yubikey Challenge-Response physical security). Remote databases stored on S3 fail to open when they are double protected by a master password and a challenge-response using KeeChallenge.

I created two databases and tested four different opening scenarios. I triple-checked to make sure all authentication information (e.g. master password, Yubikey) were correct and that wasn't the problem. In the below list "local" means the database file was stored on my machine, and "remote" means it was stored in S3 using KeeAnywhere to access it.

1. local database with only master password -> opens successfully
2. local database with master password and Yubikey Challenge-Response -> opens successfully
3. remote database with only master password -> opens successfully
4. remote database with master password and Yubikey Challenge-Response -> fails to open

The failure occurs after I enter my master password, select "Yubikey Challenge-Response" in the Key file field, and then click "OK". The message specifically reads "Error: file could not be read correctly. Is the file corrupt? Reverting to recovery mode"

That error is clearly from the KeeChallenge plugin because it prompts me to "recover" the file using my Yubikey's secret. But, since this behavior only happens with remote databases on S3 using KeeAnywhere, I'm trying to figure out if the problem is in KeeAnywhere plugin or KeeChallenge plugin. Do you have any ideas that might help me figure this out, or any diagnostics I can try to provide more information?

I can work around the problem by opening databases locally and simply backing them up to S3 manually, but that's not as preferred.

[Kyrodan]

Hmm, I have to check what KeeChallenge does. Maybe it interferes with some "magic" I use.