Live data from Hacker News

Lastpass Security Incident

blog.lastpass.com

241–250 of 587 posts

Re: Lastpass Security Incident

#241
post #184

The best is to use something like Keepassxc, synced peer to peer by Synchting or Resilio. Nobody will be involved with your passwords. Keepassxc supports Yubikey, so you can lock it down strongly!

Yubikeys (and more generally CTAP) do not really help with locking down local password managers. The KeePassXC FAQ even explicitly explains that.

Re: Lastpass Security Incident

#243

Just a reminder: if you are deciding to migrate from LastPass to something else, the password export malfunctions for unknown reasons. If you have memos, it could be a character in the memo. You must make sure the exported CSV file has everything!

Too much work. At that point, it’s easier to just hack the LastPass servers.

Re: Lastpass Security Incident

#244

Just a reminder: if you are deciding to migrate from LastPass to something else, the password export malfunctions for unknown reasons. If you have memos, it could be a character in the memo. You must make sure the exported CSV file has everything!

I migrated from LastPass years ago and ran across this error. Sounds like they still haven't fixed it.

Re: Lastpass Security Incident

#245

Earlier quoted context omitted.

Zero knowledge, 100% authority on downloaded JavaScript.

I wish there was a bigger push for integrity checking in the browser. It would be foundational to any solution that fixes that problem. There is already integrity checking for subresources: https://developer.mozilla.org/en-US/docs/Web/Security/Subres... Newcastle University had a proposal for website wide integrity checking: https://github.com/toreini/DOMtegrity Note that only 7 people have starred it on Github.

How would you approve updates to any site content in this model? Have users approve every time any embedded JavaScript hash changes?

Re: Lastpass Security Incident

#246

Earlier quoted context omitted.

Passwords suck. Move on to something better.

like what ?

It is a hard one because the only computing/memory device you have with you at all times, requires no batteries and not connected to any networks (yet) and not vulnerable to probing/observation (yet) is your brain! But memory is too unreliable unless everyone trains for it.

Crypto keys are great but you can lose them and once shared they are keys to you kingdom.

Specific security devices are great but you need to remember to have them with you. They can get lost or broken so you need backups.

Google authentication is convenient but they can ban you. It is also a 3rd party to trust.

Passwords suck but might be the best of the worst. Advantages: password managers can be used to make password useless for other sites and people conceptually understand it.

It is quite a hard problem!

Re: Lastpass Security Incident

#247
post #109
post #78

Earlier quoted context omitted.

This is years ago now, but every ampersand in my passwords came across wrong. I can't recall if it was missing or url encoded, but even passwords weren't safe.

I'm still finding passwords in Bitwarden to old accounts that have `&` in them. Thanks, LastPass!

Your password is safely html encoded for distribution on the web.

Re: Lastpass Security Incident

#248

Earlier quoted context omitted.

Does your sync setup work in realtime in the background? Earlier this year I was evaluating iOS devices and a showstopper was the apparent inability to have keepass database updates push-synced: the closest I got was a scheduled copy of the file at a given time daily, but my nightmare was making a change on one device, needing that change on the iOS device, having it not be there, and not having network to go fetch i…

No, that's a limitation in the setup but it's something I am willing to live with. I can make edits on my computer and "pull" them onto my phone, but not the other way around. However I think this is a limitation of the app itself more than a limitation of the system in principle. As far as I can tell, the developer decided to only support a couple of the most popular cloud sync platforms. Maybe guess there is no con…

Gotcha, thank you.

Re: Lastpass Security Incident

#249
post #226

I once started an interview process as a senior developer at Goto, the company behind LastPass. The contact was a first phone call where someone simply asked the number of experience I had in software development, Java programming, etc. I thought it was weird that basically all they got from the phone call was a bunch of numbers. The weirdest part tho what that they asked how many years of experience I had in... open…

You laugh at that coding assignment for a senior position but you'd be surprised how many "senior" people interview that would struggle with that and be unable to complete it.

Re: Lastpass Security Incident

#250

Earlier quoted context omitted.

> if you're satisfied with first and second factor living in the same spot It’s no longer “2FA” then.

It is still 2 factor, breaching the password manager is a corner case that you can decide to cover or not. It seems like for critical accounts you should NOT. For derived accounts, it should be better than just a password.

Only very marginally so. Or what would you say storing a (unique, long) password next to a TOTP hash actually achieves?
Post reply on HN