Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support autofilling wireless network passwords in Android #2

Open
luckyrat opened this issue Feb 5, 2022 · 1 comment
Open

Support autofilling wireless network passwords in Android #2

luckyrat opened this issue Feb 5, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@luckyrat
Copy link
Member

luckyrat commented Feb 5, 2022

Android only tells us that the password is for "com.android.settings", which is such a vague identifier that we have to ignore the autofill request entirely.

We could try removing that application ID from the permanent exclusion list and adding it to a new list of vague IDs. Applications on that vague list could be autofilled by a Kee Vault user but only temporarily - they will have to search for the desired password every time rather than us remember their preference in future like we do for most apps and websites.

@luckyrat luckyrat added the enhancement New feature or request label Feb 5, 2022
@luckyrat
Copy link
Member Author

We could also see whether the Android settings app supplies the new autofill hint AUTOFILL_HINT_WIFI_PASSWORD = "wifiPassword"; and find a way to ignore all autofill requests for that app unless a field with that hint value is present. We'd probably have to supply some additional metadata to the entries containing that password though, so that the password can be supplied to more apps than just that one Android settings app.

First step will be to inspect whether Android even uses this documented hint value in their settings app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant