• lmmarsano@lemmynsfw.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    9 days ago

    bitches don't know bout my dick

    Bitches don’t know that passkeys are awesome. It’s like ssh key authentication for web apps. Just save the passkeys to my password manager & presto: use same keys on all my devices.

    It replaces opening a TOTP app to copy a token with a click to select the passkey in a prompt from my password manager.

  • recall519@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    9 days ago

    I just wish Google would stop overriding my passkey on Android for specific apps including their own.

  • OpenPassageways@lemmy.zip
    link
    fedilink
    arrow-up
    0
    ·
    9 days ago

    Passkeys are phishing resistant, or so they say… but the web app still needs to let you in with password + 2FA… So I’m not sure how much that’s really worth.

    I guess if the users are typically never seeing a 2FA prompt then it should be more suspicious when they see one?

    • TaviRider@reddthat.com
      link
      fedilink
      arrow-up
      0
      ·
      9 days ago

      Passkeys are a replacement for passwords. Passwords don’t solve the problem of a lost password, and passkeys don’t solve the problem of a lost passkey. How a site deals with lost credentials is up to them. It doesn’t need to be password + 2FA.

  • whoisearth@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    9 days ago

    I’ll use banks as an example

    If they cared about your security there would be mobile app or website.

    Hell, credit cards would still require a signature.

    It’s about cost first and foremost and then convenience.

    Has nothing about you as a consumer. They don’t give 2 shits about you as a consumer.

    • throwback3090@lemmy.nz
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 days ago

      I mean you’re right about banks but your examples make no sense.

      Banks generally don’t support 2fa, which is bad. Some banks (fidelity) still have character limits on passwords because they stores it in plaintext until recently so you could use it through the telephone system. They could implement a secure tap to pay system on your phones with enhanced security, rather than relying on Google to handle their job. And for credit cards themselves, switch to chip and pin.

      “Banks don’t have mobile apps”?? “Signatures are secure”???🤡

      • whoisearth@lemmy.ca
        link
        fedilink
        arrow-up
        0
        ·
        8 days ago

        How easy is it to fake a signature for a normal person who has not practiced a person’s signature for the intent purpose of faking it? Have you ever tried faking your parents signature to get out of school? I have.

        Now the infrastructure required to adequately check signatures is not practical hence it doesn’t exist. It’s why we moved to pins. Pins are small and 2fa doesn’t exist for banks because again it’s about the bare minimum and they are out to make money and don’t care about customers plus there’s government safeguards in place specific to banking.

        I will continue to argue that going back in time signatures are infinitely more secure than a 4 digit pin let alone tap but we have traded security for convenience.

        Anyways full admit that I’m batshit crazy.

    • candybrie@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      9 days ago

      Do you think signatures were at all secure? If they cared about security they’d do chip+pin like most civilized countries.

      • whoisearth@lemmy.ca
        link
        fedilink
        arrow-up
        0
        ·
        8 days ago

        With proper infrastructure yes signatures are extremely secure. But that proper infrastructure doesn’t exist.

  • darvit@lemmy.darvit.nl
    link
    fedilink
    arrow-up
    0
    ·
    9 days ago

    ITT: people who think only SMS, email and TOTP exist as 2FA.

    And people who think only your phone can be used as passkey.

    • ArcaneSlime@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      9 days ago

      When those are the only options given by some services, yeh it kinda is. I’d love to be able to just use my flipper as a u2f for everything, but unfortunately most websites are all “no” and you have to use a chrome browser instead of Librewolf even when you could use a yubikey, so fine I guess text me, oh whoops I changed my number and I’m now locked out of my acct, cool.

  • Boozilla@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    9 days ago

    Remember when tap-to-pay was new and didn’t work at a lot of places and some people were freaked out over it?

    And now most of us use it without a 2nd thought.

    I speculate passkeys will be like that.

  • SleafordMod@feddit.uk
    link
    fedilink
    English
    arrow-up
    0
    ·
    9 days ago

    I have no idea what a passkey is and I will probably only learn what it is when they become mandatory

    I will just use passwords + 2FA for the moment

      • SleafordMod@feddit.uk
        link
        fedilink
        English
        arrow-up
        0
        ·
        7 days ago

        I see, thanks. It mentions biometrics on that page. Maybe if my next laptop has a fingerprint reader then I should look into passkeys more.

        • bradboimler@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          7 days ago

          I don’t use the biometric authentication on my laptop and am able to complete the demo on it. Chrome asks me for a PIN that I save and provide when it asks on my laptop. I don’t think biometrics are a requirement for passkeys.

    • jj4211@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      9 days ago

      Passkey is essentially a branding of webauthn. Instead of typing some code that changes, you just do something with some sort of device or key manager.

      Plug in a yubikey and touch the button to authenticate. Easier.

    • Swarfega@lemm.ee
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      8 days ago

      Indeed. Why so many recommend them I have no idea.

      Honestly, if you have a password manager that supports security keys then buy two cheap keys (one for backup) like the Thetis FIDO U2F Security Key and use those to secure your password vault. For everything else just use TOTP and Passkeys stored in your vault.

      I invested in Yubikeys and yes it was a waste.

      • LordKitsuna@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        8 days ago

        I’m getting ready to roll them out at work but it’s basically exclusively for the password managers. Having a password manager and every account be unique isn’t helpful if everyone’s going to just use shit passwords for their password manager

  • Randelung@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    10 days ago

    It’s not for your security, it’s for the company’s. People suuuuuuuuck when it comes to credentials.

    • NocturnalEngineer@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      9 days ago

      My company insists on expiring passwords every 28 days, and prevents reuse of the last 24 passwords. Passwords must be 14+ characters long, with forced minimum complexity requirements. All systems automatically lock or logout after 10 minutes of inactivity, so users are forced to type in their credentials frequently throughout the day.

      Yes people suck with creating decent credentials, but it’s the company’s security policies breeding that behavior.

      • Randelung@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        9 days ago

        And yet admin, 1234, test, etc. remain the most commonly ‘hacked’ passwords. Your company’s policies may be annoying, but they certainly don’t make you use unsafe passwords.

      • greenskye@lemm.ee
        link
        fedilink
        English
        arrow-up
        0
        ·
        9 days ago

        Same. They also don’t allow password managers and I have multiple systems that don’t use my main password, so I have at least 5-6 work passwords for different systems.

        Nobody can remember all that.

        So everyone makes the simplest password they can (since it has to be regularly typed in) and writes it down somewhere so they don’t forget it.

      • oatscoop@midwest.social
        link
        fedilink
        arrow-up
        0
        ·
        9 days ago

        I don’t get why people get upset at frequently expiring passwords. It’s not hard: just write it on a postit note and stick it on your monitor.

      • Tiger@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        ·
        9 days ago

        Tell them the NIST recommendations for password frequency changes have been really reduced in recent times because it pushes people into other bad password practices. Among all factors, changing the password frequently is the least important.

      • lmmarsano@lemmynsfw.com
        link
        fedilink
        English
        arrow-up
        0
        ·
        9 days ago

        My company insists on expiring passwords every 28 days, and prevents reuse of the last 24 passwords. Passwords must be 14+ characters long, with forced minimum complexity requirements.

        Outdated security practices & cargo culture. Someone should roll up a copy of NIST SP 800-63 to smack them over the head until they read it:

        The following requirements apply to passwords:

        1. Verifiers and CSPs SHALL require passwords to be a minimum of eight characters in length and SHOULD require passwords to be a minimum of 15 characters in length.
        2. Verifiers and CSPs SHOULD permit a maximum password length of at least 64 characters.
        3. Verifiers and CSPs SHOULD accept all printing ASCII [RFC20] characters and the space character in passwords.
        4. Verifiers and CSPs SHOULD accept Unicode [ISO/ISC 10646] characters in passwords. Each Unicode code point SHALL be counted as a single character when evaluating password length.
        5. Verifiers and CSPs SHALL NOT impose other composition rules (e.g., requiring mixtures of different character types) for passwords.
        6. Verifiers and CSPs SHALL NOT require users to change passwords periodically. However, verifiers SHALL force a change if there is evidence of compromise of the authenticator.

        Maybe ask them their security qualifications & whether they follow the latest security research & industry standards.