Jonathan White

Good suggestion. @varjolintu how about that message and then state: "Having trouble connecting to KeePassXC? Try our troubleshooting guide." With link there

Maybe a "See more details" type scenario?

This presents challenges if you do actually have the entry in your database, but we just don't know about it cause it's locked. Could lead to duplicate entries. BUT, not...

Not using keepassxc at all....

We are recommended by the EFF.

There is no reason for this extension on android.

We have a full suite of "getting started" documentation being developed right now for both the app and the browser extension.

If the iframe loads a different url than the one the credentials are stored in then nothing will be filled in. Presumably the attacker would not be loading the fake...

Yah I think what he's saying is that he chose login fields in the iframe but the extension still used the address bar url when saving those credentials.

Yup the workaround is Auto-Type. Every native messaging based plugin will be broken. This includes one's that talk to smart cards. Until the browser snap itself supports native messaging this...