Password managers: which do you use and why?

Started by Upsilon, Oct 07, 2026, 10:08 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Topic: Password managers: which do you use and why?   Views(Read 130 times)

Upsilon

Password managers are one of the best security tools available, yet many people still reuse the same few passwords everywhere. Data breaches happen constantly, and once one password leaks, attackers try it on every other site. A password manager creates strong, unique passwords for every account and remembers them for you. It sounds simple, but getting people to adopt one is surprisingly hard

There are plenty of options. Bitwarden is popular for being open source and affordable, while 1Password is known for polish and family features. Browsers like Chrome, Firefox and Safari have their own built in password managers, and Apple and Google keep improving theirs. Some people prefer offline options like KeePass, keeping everything in a local encrypted file

Passkeys are starting to change things too. Instead of typing a password, you log in with your fingerprint, face or device PIN, and there is no password to steal. Many password managers now store passkeys alongside traditional passwords. It may take years before passwords disappear completely, though

I switched to a password manager a few years ago after a breach exposed an old password I had reused on several sites. It took a weekend to change everything, but I have not worried about passwords since

Which password manager do you use, and why did you choose it? Any tips for persuading reluctant friends and family to try one?
ISA maxed. Costs minimised.

NightHarbour15

Apple's built in Passwords app now. It is free, syncs across my devices and the new app is much better than it used to be. Families sharing groups are a nice touch

Forge45

Passkeys are brilliant where they work. Logging in with my fingerprint is quicker than any password. Banks seem slowest to adopt them

Pilgrim11

Bitwarden. Free tier is generous, it is open source and it works everywhere. I pay for premium just to support them. Self hosting is an option too for the very keen

Orbit William

1Password for the whole family. The sharing features are brilliant for things like streaming accounts and the Wi-Fi password. It is more expensive than some, but the polish makes it easy for my parents to use. That is what matters. Watchtower alerts for breached passwords are excellent

Leo

Persuade family by setting it up for them. Nobody adopts it if they have to do it themselves. Then check in after a month to make sure they are using it. Habits take time

CosmicRay67

KeePass, with the database synced through my own cloud storage. I like keeping control of my data. It is less convenient, but I trust it

Syncthing keeps it updated across devices. Browser plugins make it nearly as easy as the commercial options
Still figuring it all out

Dylan38

Google's password manager in Chrome. Not the most secure option, perhaps, but far better than reusing passwords like I used to. Progress, not perfection. It even warns about reused passwords now, which helps

Related Topics (1)

Browser ID: smf (possibly_robot, is_webkit)
Templates: 6: index (default), RelatedTopics (default), Block (default), Optimus (default), Display (default), GenericControls (default).
Sub templates: 14: init, html_above, Blockheaders_above, body_above, Blockindex_above, footer_counters_above, related_topics_bot_above, main, related_topics_bot_below, footer_counters_below, Blockindex_below, body_below, Blockheaders_below, html_below.
Language files: 11: index+Modifications.english (default), Turnstile.english (default), RelatedTopics.english (default), Block.english (default), Optimus/Optimus.english (default), Post.english (default), Editor.english (default), Drafts.english (default), giphy.english (default), QRCode.english (default), klipy.english (default).
Style sheets: 7: index.css, attachments.css, turnstile.css, ajaxsearchlite.css, jquery.sceditor.css, show_password.css, responsive.css.
Hooks called: 290 (show)
Instances created: 14 (show)
Files included: 138 - 1847KB. (show)
Memory used: 11078KB.
Tokens: post-login.
Cache hits: 23: 0.00249s for 50,599 bytes (show)
Cache misses: 3: (show)
Queries used: 26.

[Show Queries]