You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
There are some sites like AWS that use an "account" field besides the usual username and password ones. While it would be great if Lockwise could detect it instead of overwriting my different AWS accounts passwords a more approachable would be the option to add a custom field (or fields) to our Logins.
The text was updated successfully, but these errors were encountered:
That's what I was thinking too. Also, if you're using protonmail you'll even have two passwords, one for the login and one for the mailbox.
Anyways, I think basic custom fields will do the job.
In Bitwarden, you can make custom fields. I use them for secret questions because I don't trust sites not to implement secret questions terribly. So in bitwarden, I have lots of entries like:
Mom's maiden name:
iwlekcm2893ycuaklajfhajkx23*^&*(X
I have good rapport with phone support. :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are some sites like AWS that use an "account" field besides the usual username and password ones. While it would be great if Lockwise could detect it instead of overwriting my different AWS accounts passwords a more approachable would be the option to add a custom field (or fields) to our Logins.
The text was updated successfully, but these errors were encountered: