I use 1Password, and the only incentive which make me switch is completely open source good quality UX solution.
So.. KeePassXC?
Introducing Remembear, new password manager
71–80 of 98 posts
Re: Introducing Remembear, new password manager
#72I use 1Password, and the only incentive which make me switch is completely open source good quality UX solution.
I'm working on that ( https://passit.io ) and I'm curious what your opinion of good UX is. Many here mention vulnerabilities from web extension autofill (domain matching issues, etc). Do you have any opinion between: A) No autofill. Copy and paste (but good simple shortcuts). Least attack vectors, but least convenient. B) Autofill but only when user prompts (with shortcut). This avoids having to inject js into web pa…
Re: Introducing Remembear, new password manager
#73From the Cure53 report: the version tested had a terrible vulnerability (unfortunately somewhat common to password managers): it tries to match passwords to subdomains, and in doing so misparses domains, allowing it to be tricked into giving passwords to bogus almost-look-alike domains. Yikes. Meanwhile: they've got a crypto protocol tunneled over TLS "to avoid heartbleed" and some other convoluted stuff the auditors…
I’m holding my breath...
Re: Introducing Remembear, new password manager
#74From the Cure53 report: the version tested had a terrible vulnerability (unfortunately somewhat common to password managers): it tries to match passwords to subdomains, and in doing so misparses domains, allowing it to be tricked into giving passwords to bogus almost-look-alike domains. Yikes. Meanwhile: they've got a crypto protocol tunneled over TLS "to avoid heartbleed" and some other convoluted stuff the auditors…
"Schneier on Security: Security of Password Managers" https://www.schneier.com/blog/archives/2014/09/security_of_p...
Re: Introducing Remembear, new password manager
#75Re: Introducing Remembear, new password manager
#76From the Cure53 report: the version tested had a terrible vulnerability (unfortunately somewhat common to password managers): it tries to match passwords to subdomains, and in doing so misparses domains, allowing it to be tricked into giving passwords to bogus almost-look-alike domains. Yikes. Meanwhile: they've got a crypto protocol tunneled over TLS "to avoid heartbleed" and some other convoluted stuff the auditors…
> This is pretty unusual for Cure53, who have a reputation for being a bit effusive about the products they're paid to review. I'm not sure I've ever seen them throw shade before. Yes, and it's getting really old. I'm tired of seeing security consulting firms wax poetic about how good the client's security is in their reports, then bend over backwards to frame obviously serious findings in the best possible light. Th…
it's an industry secret that one of the reasons you do an audit is so you don't have to publish the "real" findings
Re: Introducing Remembear, new password manager
#77Earlier quoted context omitted.
Ohh I like the idea of knowing the password requirements for the top 1000 websites!
Would it be wrong to wish this could (or should?) be standardized? That is, for example, one upper case letter, same special characters, etc. The lack of a standard seems to hurts users more than hackers. The hackers know it and adjust. User just get confused and default to overly simplistic and common PWs.
This file could define the accepted password format. Password managers could retrieve that file and know exactly how to generate a password.
Re: Introducing Remembear, new password manager
#78Earlier quoted context omitted.
Can you recommend any reputable open source password managers?
KeePass, pass, PasswordSafe, KeePassXC, bitwarden, enpass
Re: Introducing Remembear, new password manager
#79Earlier quoted context omitted.
Would it be wrong to wish this could (or should?) be standardized? That is, for example, one upper case letter, same special characters, etc. The lack of a standard seems to hurts users more than hackers. The hackers know it and adjust. User just get confused and default to overly simplistic and common PWs.
There should be a "robot.txt" for passwords. ie: /password.txt This file could define the accepted password format. Password managers could retrieve that file and know exactly how to generate a password.