5 ms·

Another thread on the incident report here: https://news.ycombinator.com/item?id=11664713 https://news.ycombinator.com/item?id=11664713 https://status.uservoice

Another thread on the incident report here: https://news.ycombinator.com/item?id=11664713 https://news.ycombinator.com/item?id=11664713 https://status.uservoice.com/incidents/fb7ml8b3nphf https://status.uservoice.com/incidents/fb7ml8b3nphf There's a bit more info in this one about exactly what was compromised though. While I can understand the abundance of caution in resetting passwords despite only hashes and salts being lost, it is odd that they would "[presume] the attackers may be able to decrypt the passwords," assuming they're using strong encryption.

runesoerensen 11y ago
I wouldn't call resetting passwords an "abundance of caution" in this case. It's very likely that the attackers are able to retrieve passwords when they have the SHA1 hash and the salt (not exactly by decrypting though). Here's a good blog post how and why this is problematic: https://www.troyhunt.com/our-password-hashing-has-no-clothes/ https://www.troyhunt.com/our-password-hashing-has-no-clothes...
- tempestn 11y ago
  Do they say somewhere that they're only using sha1 though? That's sort of what I meant: if bcrypt or scrypt is used, with an appropriate work factor, the risk should be very minimal. The fact that they're assuming it's not suggests they are using weaker encryption.
  - runesoerensen 11y ago
    Yes they said that in the first paragraph of the incident report you posted a link to ;) Unfortunately, the passwords were hashed with the SHA1 hashing algorithm, which by today’s standards is considered weak Also, hashing != encryption
    - tempestn 11y ago
      Ahh thanks. I read the email they sent out, which had very similar content, but omitted that bit. Just skimmed the post itself, but obviously missed that key info. Interesting that they don't include strengthening their encryption (ok, hashing) in the list of steps they plan to take, but presumably they will.
      - runesoerensen 11y ago
        From the same incident report: When users reset their password, we’re going to be hashing it with the bcrypt algorithm with a strong cost value.
        tempestn 11y ago
        My god, I swear they're ninja editing the thing on me! I'm really not normally someone to comment before RTFA. Thanks for patiently leading me through it. :P

runesoerensen 11y ago

I wouldn't call resetting passwords an "abundance of caution" in this case. It's very likely that the attackers are able to retrieve passwords when they have the SHA1 hash and the salt (not exactly by decrypting though). Here's a good blog post how and why this is problematic: https://www.troyhunt.com/our-password-hashing-has-no-clothes/ https://www.troyhunt.com/our-password-hashing-has-no-clothes...

tempestn 11y ago
Do they say somewhere that they're only using sha1 though? That's sort of what I meant: if bcrypt or scrypt is used, with an appropriate work factor, the risk should be very minimal. The fact that they're assuming it's not suggests they are using weaker encryption.
- runesoerensen 11y ago
  Yes they said that in the first paragraph of the incident report you posted a link to ;) Unfortunately, the passwords were hashed with the SHA1 hashing algorithm, which by today’s standards is considered weak Also, hashing != encryption
  - tempestn 11y ago
    Ahh thanks. I read the email they sent out, which had very similar content, but omitted that bit. Just skimmed the post itself, but obviously missed that key info. Interesting that they don't include strengthening their encryption (ok, hashing) in the list of steps they plan to take, but presumably they will.
    - runesoerensen 11y ago
      From the same incident report: When users reset their password, we’re going to be hashing it with the bcrypt algorithm with a strong cost value.
      - tempestn 11y ago
        My god, I swear they're ninja editing the thing on me! I'm really not normally someone to comment before RTFA. Thanks for patiently leading me through it. :P