No KeePassDX autofill suggestions

Stephan-P

Indeed, great detective work.
Too bad this forum doesn't support inline images. It would have made things much easier understanding each other.
I will go through my database hunting for trailing slashes and or subdirectories, thus removing potential barriers.

de0u

Stephan-P Too bad this forum doesn't support inline images. It would have made things much easier understanding each other.

True. Sadly, it would also make the forum more usable for spammers.

Stephan-P

Stephan-P Indeed, A LOT of trailing slashes in my KeePass database to be removed....

Stephan-P

So, I set on removing all trailing slashes from the urls in my KeePassDX/KeePassXC database yesterday evening. This morning I'm getting no password autofill suggestions in Vanadium at all.

Switching to Vivaldi, password autofill suggestions are provided and logging in is supported by KeePassDX as it should be.
Vivaldi is doing things right where Vanadium is dropping the ball somewhere.

IcyScroll

Deleting the trailing slashes seems to have fixed the issue for me. Thanks for your work @ToffoliGate!

Will report if the problem comes back. I don't depend on this feature as much as @Stephan-P so it might take more time. It's definitely nice to have it working, though!

lGsgw0

The problem might even be a different one. I'm running latest GrapheneOS (Android 15) on Pixel 6 and got no Google Play services installed on my main profile. The web browsers tested are:

Fennec
Brave (through Aurora Store)
Cromite
Vanadium

Autofill always works with Fennec and KeePassDX (I tried versions 4.0.8 from Aurora Store, 4.1.0 and 4.1.1 Libre and Free from F-Droid / IzzyOnDroid).

Brave has chrome://flags/#enable-autofill-virtual-view-structure "Enabled without any compatibility check" to show the "Autofill services" entry under its Settings; with "Autofill using another service" + appropriate "Android Settings" selected. Optional chrome://flags/#web-authentication-android-credential-management is "Enabled for Google Password Manager and 3rd party passkeys". Not sure if #show-autofill-type-predictions and #enable-show-autofill-signatures would also be of interest, hence I left both Disabled.

Cromite has "Enable native Android autofill" put ON and Vanadium its "Autofill services" adjusted.

KeePassDX's autofill just won't work on Brave, Cromite and Vanadium. Same behavior was observed on stock Pixel 9 with Brave and Cromite. Gboard and HeliBoard both made no difference. Keepass2Android however works in all these scenarios! Strangely just after playing around with Keepass2Android and then selecting KeePassDX as "Preferred service" on GrapheneOS, even KeePassDX started to show entries...

So the "fix" for now seems to be using Keepass2Android (version 1.11-r0) instead of KeePassDX ( https://github.com/Kunzisoft/KeePassDX/wiki/AutoFill is outdated).

Can anybody confirm the same?

lGsgw0

lGsgw0 This part is outdated, I meant: https://github.com/Kunzisoft/KeePassDX/wiki/AutoFill#compatibility-mode

lGsgw0

lGsgw0 lGsgw0 PS: Cromite ( https://github.com/uazo/cromite ) remains to be the only through F-Droid available and regularly maintained option, which offers all of the mentioned features but unfortunately, not (yet) to the class-leading standards of Brave. Keepass2Android works to the previously described extent.

It would really be great if Vanadium borrowed some of its features! :-) @GrapheneOS

Stephan-P

I've given up on Vanadium in combination with KeePassDX. Where autofill login is required, I'm now using my favourite browser Vivaldi.

lGsgw0

Stephan-P Would you mind trying with Keepass2Android ( https://github.com/PhilippC/keepass2android )? Backup your KDBX file first.

Just to narrow the issue down. It works in my case as described above. Maybe it is related to how KeePassDX handles the data, hence a bug, opposed to how Keepass2Android does.

Stephan-P

lGsgw0 Brief experiment with Kp2A and Vanadium logging into this forum.

Kp2A does not offer autofill on username field.
Kp2A does offer autofill on password field, and fills only the password field

Switching back to KPDX and Vivaldi as defaults

lGsgw0

Stephan-P Thank you for your feedback!

Kp2A does not offer autofill on username field.

...seems to be website specific and is something that might be addressed by the package maintainer.

I did a few more tests and found that for example, on https://discuss.grapheneos.org/ Keepass2Android does not fill the username but on https://community.brave.com/ it works flawlessly with both the username and password fields. It is annoying but at least in can be overcome by the password managers' specific keyboards (Keepass2Android keyboard or Magikeyboard in case of KeePassDX).

I would prefer to use KeePassDX but my conclusion thus far is that its autofill doesn't work in the majority of cases (besides on Gecko-based web browsers). Keepass2Android instead works even without Google Play services and has just some minor issues.

====
Vivaldi is a very nicely built web browser but sadly cannot be configured in such way to work independently from Google services. This close attachment to Google rules it out for me personally; see following analysis of the desktop version (won't be a lot different on mobile OS). Translate with your preferred service but Google might be blocked: https://www.kuketz-blog.de/vivaldi-datensendeverhalten-desktop-version-browser-check-teil5/

Furthermore it remains to be seen how Vivaldi manages the Google Manifest V3 "update" ( https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-future-proofed-with-its-built-in-functionality/ ) vs. how Brave ( https://brave.com/blog/brave-shields-manifest-v3/ ) and others do.

Vanadium is really great especially for its hardening and user friendliness but lacks state-of-the-art fingerprinting protections and a comprehensive Ads-/Trackers/Malware blocker.

Brave delivers in both ways, with possibly the strongest fingerprinting protections just after Tor- and Mullvad Browsers (Mullvad only for desktop OS) and can be configured for privacy friendly use (additional blocking of "variations.brave.com" and "star-randsrv.bsg.brave.com" through a DNS filter required).

In any case using Aurora Store, the following might require mitigation, depending on ones personal needs: https://gitlab.com/AuroraOSS/AuroraStore/-/blob/master/POLICY.md

Gecko-based web browsers like Firefox and Fennec instead, don't include Site Isolation on Android ( https://www.chromium.org/Home/chromium-security/site-isolation/ ) and don't set the isolatedProcess flag ( https://developer.android.com/guide/topics/manifest/service-element#isolated ). They only offer Site Isolation on desktop OS ( https://wiki.mozilla.org/Project_Fission ). Hence, of all the available options only the Tor Browser remains a good choice for its specific use cases.

I'd wish KeePassDX would at least work to Keepass2Android's extent. :-/

« Previous Page