{"id":1932,"date":"2012-06-07T12:20:33","date_gmt":"2012-06-07T11:20:33","guid":{"rendered":"http:\/\/t-machine.org\/?p=1932"},"modified":"2012-06-07T12:20:33","modified_gmt":"2012-06-07T11:20:33","slug":"linkedin-maybe-just-leaked-your-password-wont-tell-you-change-it-now","status":"publish","type":"post","link":"http:\/\/new.t-machine.org\/index.php\/2012\/06\/07\/linkedin-maybe-just-leaked-your-password-wont-tell-you-change-it-now\/","title":{"rendered":"LinkedIn (maybe) just leaked your password, won’t tell you; change it now"},"content":{"rendered":"

I’ve posted a few times over the years the … disappointing … state of LinkedIn’s engineering. But this takes the biscuit: it appears they were storing deliberately insecure passwords, and someone leaked the list:<\/p>\n

http:\/\/news.ycombinator.com\/item?id=4073309<\/a><\/p>\n

(that page has links + info on how to check if your own password is in the mega list)<\/p>\n

How bad is this?<\/h4>\n
    \n
  1. Many people have checked their personal, unique, passwords, that they claim to have only ever used on LinkedIn.com – and they’ve hit matches in the file.\n
  2. LinkedIn hasn’t told its users about the possible leak, more than 24 hours after it happened\n
  3. Many users re-use their passwords on other sites; any hackers could easily have stolen many accounts on other sites by now\n<\/ol>\n

    How unlucky is LinkedIn?<\/h4>\n

    This file is unsalted. That’s about as smart as locking your front door and then leaving the key under the mat – on the outside.<\/p>\n

      \n
    1. Every tutorial, book, “newbie guide”, etc about using databases and writing login pages tells you never ever to do what was done here\n
    2. For any tech team, it is easy to check if this is what you’re doing, and tell your boss “uh, we need to fix that”\n
    3. It only takes a few *minutes* to prevent this problem, permanently. It’s not difficult\n<\/ol>\n

      If LinkedIn were a small site, with a few hundred thousands users, I’d accuse them of laziness. But with 165million users, and a public company, you’d be looking at stunning incompetence by the tech wing of the company (the CIO and CTO never bothered to audit their own security?), or wilful negligence (no-one knew? really?).<\/p>\n

      Here’s hoping it’s a hoax…<\/p>\n","protected":false},"excerpt":{"rendered":"

      I’ve posted a few times over the years the … disappointing … state of LinkedIn’s engineering. But this takes the biscuit: it appears they were storing deliberately insecure passwords, and someone leaked the list: http:\/\/news.ycombinator.com\/item?id=4073309 (that page has links + info on how to check if your own password is in the mega list) How […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[33,20,6],"tags":[],"_links":{"self":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts\/1932"}],"collection":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/comments?post=1932"}],"version-history":[{"count":0,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts\/1932\/revisions"}],"wp:attachment":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/media?parent=1932"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/categories?post=1932"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/tags?post=1932"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}