Renoir Boulanger
My feedback
1 result found
-
281 votes
An error occurred while saving the comment
Renoir Boulanger
1 result found
Renoir Boulanger
supported this idea
·
Category or directory is great for the main kind.
But with tags we can reuse between entries help with managing complexity.
- Tag is any word(s)
- Describe the meaning we’re giving it
- optional note
Because at the moment to organize we have either to use note field, re-reate custom field manually, or cram info in the password entry name (and often forget the tags we’ve created and their meaning)
For example:
- “Crit;” Critical accounts (things that many other things depend),
- “UnU;” Unused (for accounts we can’t delete but don’t want compromised because we can’t change fields we want to make private or can’t delete the account because the site doesn’t support),
- “MFA;” MFA (has a TOTP authenticator secret),
- “MFAPSK1;” (Has MfA but with a Physical Security Key, the #1 is bound to this account. We will have many FIDO2 hardware tokens over time not only one, and probably not all be paired)
Those labels and cryptic words are because we have to cram them in some way in the entry name.
For example, I’d have entries looking like:
- “SM Meta Facebook ~[MFA;MFAPSK1;Identity;”
- “AirCanada / Aeroplan / Bob”
- “AirCanada / Aeroplan / Alice”
- “Amazon AWS ~[Firewall;MFA;MFAPSK1;PSK;”
- “Amazon Audible ~[Subscribed;”
- “Netflix ~[Sub;UnU;MFA;”
- “Adobe Photoshop CS ~[SL;MFA;”
- “Microsoft GitHub ~[Repo;MFAPSK1;SC;”
- “GitLab ~[Repo;MFA;SC;OSS;”
- “Atlassian Bitbucket ~[Repo;SC;”
- “IBM RedHat Quay.io ~[Repo;OSS;”
In the above, I want to make sure all social media are sorted together (in the same vault or not), and Meta has many. The ~[ is to say that the rest of the name is a semi-colon separated list of acronyms
Having a tag, optionally link to a note, but importantly tell what the tag mean would be amazing!
The feature doesn’t have to be too complex. Just words or acronyms we can create, and tell our own meaning and tick per password entry.
Would be useful too for password hygiene and chores such as when we might need to phase out a YubiKey for another.
There are other types of labels/tags we might want:
- Subscriptions we are keeping,
- Subscription service we are no longer using,
- Manufacturer we want to keep a relationship for recalls and product support
- Governement for taxes, water bill, income tax, city tax, - Governemental or municipal services, such as Library, etc.
- Home Service provider for things related to home: Internet Service provider, Cell phone, Electricity, TV, Gas,
- Work related things
- MFA and which a physical (YubiKey 1, or …) or a time based and where (YubiKey stored TOTP, or 2FAS, or another Authenticator app)
- Linked with (or Login with) which account, we may have more than one Google,Apple,Microsoft account and bound login to it for authentication, how can we keep track which ones depend on which account
- Linked with Facebook account, or LinkedIn, or X-Formerly-Twitter (same as above)
- Passwordless, supports passwordless but mot used, etc.
- Passkeys and which? Is it with iCloud, the main one, or it’s with Hello, or FIDO2 or another way? (Similar to passwordless, but different wording)
- support Physical Security Keys but we haven’t paired one yet
- Which set of security questions (maybe a link to a note for that tag) so we can make up our answers instead of using real life that appeared in a data breach and have now to change
- Incomplete password hint some Critical account, maybe we would prefer not store the full password. Leave a hint. Maybe that unsaid hint is for a complex unique password and is the suffix at the end.
- Repositories where we push code or packages or images
- Open Source Software repository from which we push open source contributions and push maintenance we make