|
|
|
|
|
|
by harshreality
5125 days ago
|
|
|
Playing Devil's advocate (as in, I agree with you, site A should never under any conditions ask people to enter their password for site B): Lastpass does encourage visitors to that page to change their LNKD pw on LNKD and anywhere else it might be reused. The checker form is placed below that recommendation. Anyone inclined to enter their (old?) LNKD pw on the Lastpass page would probably enter it on some other "leakedin" password checker page that's less secure. At least Lastpass tries to be trustworthy. Regarding your point (2), I don't think it matters if the LNKD vulnerability has not been patched. Everyone should still change their LNKD pw, because the compromise might have been temporary. I agree that Lastpass and everyone else encouraging a LNKD password change should emphasize not to reuse passwords, but universally, and not specific to LNKD. |
|
|
That said, I have not dwelled to details of how LastPass handles the site design to avoid unintended leaks, (I believe the issues with leakedin are simply unintended mistakes rather than attempted malice) but I sure as hell would avoid using or recommending their services should I find mishandlings of the data within such trivial applications.
About (2), It matters in the sense, that we have to assume that all of the sensitive data which has been leaked before will continue leaking until they have identified the vuln. The worst thing a user can do, is to insert a recycled password and consider the situation resolved.
Should the hacker still have the backdoor open, he'll just steal the new keys as well. Salting helps a bit, but it's far from solving the problem.
What I'm proposing is that people should change the pw twice. First instantly (and not recycling) and then when LNKD has confirmed that this individual attack vector has been closed.