Live data from Hacker News

What’s in a PR statement: LastPass breach explained

palant.info

61–70 of 292 posts

Re: What’s in a PR statement: LastPass breach explained

#61
post #33

Why did people think that using a cloud based password manager (or for that matter: a closed source one) was ever a good idea?

Because there needs to be a baseline level of convenience in order to get less-technical people to even consider using a password manager at all.

If the alternative is using the same handful of weak passwords for every site, the risk of your password manager suffering a security breach doesn't look so bad in comparison.

Re: What’s in a PR statement: LastPass breach explained

#63

I wasn't quite ready to self promote this but I will go ahead anyway, since people are probably researching alternatives now. I'm working on a comparison of different password managers. https://password-manager.soft-wa.re/ At this point it's mainly a fork&merge of some previous work. If you find any issues with the data please submit a PR. Edit: I am standing on the shoulders of giants. Take a look at the contributor…

Please change your domain, looks like a phishing website. I would never clic on that anywhere else on the internet.

Re: What’s in a PR statement: LastPass breach explained

#64
post #13

The know it all tone of this article is kind of annoying. Security professionals seem to have a common trait of thinking they know better. Some good points in there, but limited pragmatism.

I disagree, this article did not come off this way to me, as all the comments were brief and backed up with supporting materials. In addition, the usage of words that would convey feelings the author had about the company were nonexistent — they described the actions taken (or not taken) by the company and left the reader to come to their own conclusions.

Agreed. The tone was objective and factual. It's too bad the owners of LastPass failed to heed the criticisms that preceded this incident. FYI for anyone carping about LP's legal liability here: read the disclaimers (and indemnification agreement) in their TOS (personal or business). It's a real howl, and pretty much software industry standard.

Re: What’s in a PR statement: LastPass breach explained

#65
post #58
post #28

Earlier quoted context omitted.

Disclaimer : I am the author of this article. What kind of pragmatism would you prefer? LastPass messed up way more than they are willing to admit. And it’s not like nobody warned them before, quite a few of the issues which turn out to be very problematic now aren’t news – I brought them up years ago as did others. LastPass should be warning users now and suggesting mitigation steps, instead they claim that nobody h…

This is a compelling article, I feel more motivated now to reconsider my options. FWIW, my $0.02 feedback on pragmatism: as a user, it would be nice to have more what-to-do-about-it for non-security-experts. Also I didn’t love the parts of the article where you speculated about LastPass’ motivations and process (even if they turn out to be true!) The opening paragraph is making assumptions about the timing, which cou…

Thing is: this is the third article on the topic I wrote in the past few days. Covering your options wasn’t the goal here, it’s in the first article: https://palant.info/2022/12/23/lastpass-has-been-breached-wh.... Particularly the “executive summary” at the start.

As to the “speculations”: I have sufficient experience with LastPass press releases to assume the worst whenever they omit details that they should definitely know. On a number of occasions they covered security vulnerabilities that I found, and I know how they operate.

Mind you, I would be more than happy to learn that I’m wrong. But this isn’t a situation where “hope for the best” is a viable approach.

Note: I did not claim that LastPass is storing master passwords. They claim that they built their system in a way that they cannot. And I merely point out that this isn’t true: they could have built their system in such a way, but they chose not to, despite being warned about it repeatedly.

Re: What’s in a PR statement: LastPass breach explained

#66
post #51

Catastrophic breach after catastrophic breach since 2011. Lastpass has failed their fiduciary duty as a steward of sensitive information and IMO exhibited gross negligence in not encrypting URI data, ostensibly as a trade off for consumer functionality. not to be overly vindictive, as I understand the near impossibility of running a perfectly secure service at absolutely enormous scale…but does anyone else feel LastP…

They could might as well dissolve the whole company. Most, if not all of their products are very security sensitive.

Aa long as they have paying customers that are ignorant, willing or not, to the issues I suspect they'll keep chugging along.

Re: What’s in a PR statement: LastPass breach explained

#67
post #56

Earlier quoted context omitted.

Self-hosted instance of Bitwarden works pretty well, and you can make it accessible behind a VPN to your local network only (plus there are multiple implementations of its back-end). Less-automated solutions make impractical concessions in usability. Reference impl. in C#: https://github.com/bitwarden/server Self-host friendly impl. in Rust: https://github.com/dani-garcia/vaultwarden p.s.: reference implementation is…

I always found running 12 containers for hosting a password repository a bit overkill. https://bitwarden.com/help/install-on-premise-linux/

Have you checked the second link? (emphasis on "self-hosted friendly impl.").

The first one is obviously not designed to serve as a primary self-hosted option but rather to scale for large number of users.

Re: What’s in a PR statement: LastPass breach explained

#68

Earlier quoted context omitted.

Great overview! I think 1Password's Linux support has been improving [0]. I use 1Password with an Ubuntu desktop and have been happy with it. [0]: https://support.1password.com/explore/linux/

You can submit a PR here. https://github.com/Soft-wa-re/password-manager-comparer

Thanks for providing the detailed comparison among the many password managers. I think it's more accurate to describe 1Password's CLI as "yes" rather than "yes?poor" and submitted a PR for consideration: https://github.com/Soft-wa-re/password-manager-comparer/pull...

Re: What’s in a PR statement: LastPass breach explained

#69

I'm not sure about the insight. But i hate the UI, UX of Lastpass. Why it's so hard to change for simplicty and ease of use ? Is it dark pattern, is it technically impossible due to technical architectural complexity, or tech debt,.. ? At least the UI tells me something about the internal.

No idea what you're talking about. I manage LastPass for 200 not very tech savvy users and no one has any problems using it.

Re: What’s in a PR statement: LastPass breach explained

#70

I'm really curious what people in the know have to say about PM's in general and what the good options are. I personally really love having an in-browser password manager. It's an incredible convenience and it lets every service have a unique and nearly impossible to crack password. I have far too many services to remember them all, and using the same password for everything would be terrible. But of course I see the…

I have a small script that does hash(key + masterPasswd). key is usually just the site's domain name. I have the script and a few of the important passwords (eg my email) written down on paper in case my drive dies. It works fine for me.

You just exposed all your passwords to bruteforcing attacks. Unless “hash” in this case is something like scrypt with sane parameters.

Originally (before I started writing my own password manager) I also thought that this is a safe method of password generation. And then I realized that it isn’t. Wrote about it here: https://palant.info/2016/04/20/security-considerations-for-p...

Post reply on HN