LastPass security breach linked to $35 million stolen in crypto heists
www.theverge.com
Researchers found that almost every victim was a LastPass user.

More than $35 million has been stolen from over 150 victims since December — ‘nearly every victim’ was a LastPass user::Security experts believe some of the LastPass password vaults stolen during a security breach last year have now been cracked open following a string of cryptocurrency heists

  • @charlesEnglish
    3•1 year ago

    Is there a recovery process if your yubikey breaks?

    • RootiestEnglish
      2•1 year ago

      Having a recovery process for the YubiKey would really just be a potential security hole.

      Ideally you have a backup clone of the key in case yours is lost/broken.

      Keeping a recovery seed or backup password instead would be inherently less secure as the YubiKey uses an HMAC challenge-response key for KeePass rather than a static password/key file.

      A static password or key would be a better target for hackers as it would be easier to crack so having that option would lower your overall security.

      Also worth noting that the way KeePassXC handles the HMAC challenge-response is different from how KeeChallenge does it.

      In KeeChallenge the HMAC secret is used to encrypt the database, which requires storing the encrypted secret in a separate file.

      In KeePassXC the database’s seed is used as the challenge and the response is used to encrypt the database.

      The benefit to the KeePassXC method is two-fold:

      • It’s less vulnerable as the HMAC secret never leaves the YubiKey or get stored in a file.

      • It increases security because the challenge-response changes every time you save the database (changing its seed)

      • @[email protected]English
        1•1 year ago

        Thank you for your detailed responses - I’m going to look into KeePass and maybe a Yubikey after reading your description of how it works. I hadn’t considered a Yubikey before mostly because I’m prone to lose things, but also because my encrypted file password is >12 characters and a fairly random mix of lower and uppercase letters, numbers and special characters.

    • @[email protected]English
      2•1 year ago

      There is no recovery if you have a single hardware token in use only. But that’s a structional issue with your concept.

      Instead, it is recommended to have two (or more) identical Hardware Tokens to replace one that dies.

      It is also smart to keep the seeds for things like 2fa in some secure backup with schizophrenic paranoia proof Security measures.