We wish we had all site's certificate fingerprints from before this started so we could utilize that data -- if anyone has it, an email to securit@lastpass.com would be greatly appreciated.
132 karma · joined September 4, 2010
We wish we had all site's certificate fingerprints from before this started so we could utilize that data -- if anyone has it, an email to securit@lastpass.com would be greatly appreciated.
Our choice could be to not allow people to utilize the website but it seems like educating people of the risks and letting them decide is the best policy.
Using the extensions to login -- it doesn't matter nearly as much if you're MITM as it would if the website was MITM and you login from the website -- what's in the middle is mostly useful only to do things like mess with you -- delete your sites / DOS your account, but in no way exposes your encrypted data.
The combination of extension use instead of going to the website, perfect forward security, data that's encrypted with a key that doesn't leave your devices, the fact that what you'd most likely leak is a session ID which will be replaced on your next login and that we haven't actually seen anyone utilize heartbleed to get a SSL key yet combine to make LastPass a tough target.
Given everything it'd be far easier to target all the banks and email clients that simply send your credentials right over the wire.
This is definitely a big problem and we're currently working on tools to try to help people recognize what's at risk and help them update it.
- Full time developer (we support everything so be ready to play with everything) - Full time support analysts
Email jobs at lastpass.com - CC joe at lastpass.com, and mention hacker news.
The corporate tax rate is very high and should really be thought of as 35% if you have meaningful profit.
You may also be able to defer profit if you're delivering service after you're paid for it (and you should be doing this), this keeps more money in the company without paying the taxes immediately. A far more important lesson.
They also failed to utilize the two different free multi-factor options LastPass offers (not to mention the premium ones).
LastPass tries to educate people and push them on not utilizing the same password anywhere with a security challenge, but that clearly didn't teach the concept here.
Their last breach involved losing access to their email: info@bitcoinica.com -- so what email did they use here with LastPass? info@bitcoinica.com They didn't utilize the security email either.
It is all unbelievable.
How do we drag this out of cargo cult security?
I see some are pushing certifications; If I made a free LastPass certification that both proves you understand the concepts, and that you're currently putting them into practice by showing that you/your company has multi-factor enabled would people demanded it?
What kind of Luddite computer programmer is against using computer programs to solve their problems? Yet is fine with using SSH keys?
The argument of bloat is garbage -- you can utilize LastPass bookmarklets at the cost of exactly 1 bookmark in your browser. That adds a 1K bookmark and a very small amount of JavaScript to the page if and only if you utilize it.
Password certainly are painful, and our whole goal at LastPass is to make it easier. We'd be happy to help make other scenarios people are experiencing better, we've looked at handling ssh a number of times (putty in LastPass for Applications for example) -- anyone have a preference for how we tackle that next?
I'm not defending them, many of their practices are loathsome, but crucify them for what they've actually done.
LastPass / Xmarks
Want to play with every new toy that comes out and make apps for them?
Joe@LastPass.com
2) My ranked sources are weird -- google.pl is one of the top sources.
3) My topic cloud has URLs in it which looks... bad.
4) LastPass must be broken up into Last Pass in places as Ben Rothelsberger is prominent in LastPass' topic cloud.
Good luck!