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

Alternative account filtering strategy #518

Open
NicolaSmaniotto opened this issue Oct 18, 2022 · 0 comments
Open

Alternative account filtering strategy #518

NicolaSmaniotto opened this issue Oct 18, 2022 · 0 comments

Comments

@NicolaSmaniotto
Copy link

It would be useful to select how the database entries are considered compatible with a website.

My password store is structured with /url/account, and inside that file is the password.

I'd like to have passff only look at folder names, since the account name is often an email and it contains a domain too.

Example

  1. Have eample.com/user@example.com in the password store
  2. Use the email account to register on site A, with the file A/user@example.com
  3. Open example.com

Current behaviour

Passff lists both example.com/user@example.com and A/user@example.com in the contextual search and field options

Desired behaviour

Have passff check the folder names only, so that on mail.com it would only try to autocomplete with example.com/user@example.com and ignore A (to reduce false positives)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants