• anguo@piefed.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 days ago

    Github only asks me for (bitwarden’s) passkey. That’s just a single factor.

    • Fushuan [he/him]@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 days ago

      I wouldn’t classify passkeys as MFA tho, they are a passwordless method that’s more secure than most MFA methods. Afaik it’s based on signed certificates or something like that and that’s virtually unhackable unless someone gets physical access to your device (and that’s game over anyway).

      • anguo@piefed.ca
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 days ago

        But bitwarden uploads it to the cloud to be used on any computer, AFAIK.

        • Fushuan [he/him]@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 days ago

          Bitwarden uploads the whole vault (the whole json of passwords, passkey codes, MFA identifiers, credit card info…) encrypted with your master password. Meaning that whatever is on the cloud should be virtually unbreakable. That’s why every time you write the password in the extension or Android app or whatever it takes a second or two to open, because it’s downloading and decrypting everything locally.

          When you update a password they need to reencrypt the whole vault and re-upload it again even though it’s wasteful since that’s their whole security plan.

    • Passerby6497@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 days ago

      A securely stored modern certificate is going to be magnitudes more secure than password plus MFA.

      The certificate path uses cryptography to prevent disclosure of your secret, and can’t be compromised when the site inevitably gets hacked.