Comment on Concerns Raised Over Bitwarden Moving Further Away From Open-Source

• ilmagico@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  From a quick search, Keepass2Android doesn’t have it, not clear if they’re working on it: github.com/PhilippC/keepass2android/issues/2099

  KeePassDX similarly has an open issue, not clean when/if it will be implemented: github.com/Kunzisoft/KeePassDX/issues/1421

  Good to know about Strongbox on iOS, though I’m on android so no bueno for me.

  source
• anamethatisnt@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  Keepass2Android doesn’t have it yet, but seems to be working on it
  github.com/PhilippC/keepass2android/issues/2099

  Strongbox seem to have their implementation done for iPhone
  strongboxsafe.com/updates/passkeys/

  source
• ilmagico@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  I don’t use passkeys so I don’t know. Maybe I should research into passkeys, what’s the benefit over plain on (long, randomly generated) passwords?

  source

  • jqubed@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    I’m no expert in this but the passkeys really on some sort of public key, cryptographic pair. Your device will only send your encrypted cryptographic secret when it gets the correct encrypted cryptographic secret from the destination. This makes it much harder to steal credentials with a fake website or other service.

    source
  • ilmagico@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    Ok, from a quick search, it seems passkeys rely on some trusted entity (your browser, OS, …) to authenticate you, so, yeah, I’m not sure if Ilike that. The FIDO alliance website is all about how easy, convenient and secure passkeys are, and nothing about how they actually work under the hood, which is another red flag for me.

    I’ll stick to old-fashioned, long, secure, randomly generated passwords, thanks.

    source

    • 4am@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      Passkeys rely on you holding a private key. The initial design was that a device (like a browser or computer/phone) stored the private key in a TPM-protected manner, but you can also store it in a password manager.

      This is more secure than a password because of the way private/public key encryption works. Your device receives a challenge encrypted with the public key, decrypts with the private key and then responds. The private key is never revealed, so if attackers get the public key they can’t do shit with it.

      Just be sure that your private key is safe (use a strong master password for your PM vault) and your passkey can’t be stolen by hacking of a website.

      source

      • ilmagico@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

        I see, that makes sense and should be more secure, in theory. Thanks for the explanation.

        The issue I have is, whether I need to trust a third party with my private key, e.g. Google with Android, Microsoft with Windows, etc. (yes on linux it’s different, but that’s not my only OS).

        Also if the private key does get compromised (e.g. local malware steals it), hopefully there’s an easy way to revoke it.

        source

        • -> View More Comments
    • ilmagico@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

      I was finally able to find some technical detail on passkeys on FIDO website, and yeah, it actually looks like it’s a real improvement over passwords: it’s simple, uses proven technology (public/private keys), and should be much more secure than passwords.

      Also, nothing in the “specs” says I need to entrust my private key with the OS or a third party, which is good.

      That said, it seems some OS support is required nonetheless, to show the pin / biometrics prompt (or is it?), and on android at least, I’d need to buy a new device with Android 14 to use a non-Google passkey provider…

      source