Here is the text of the NIST sp800-63b Digital Identity Guidelines.

  • jj4211@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    ·
    5 hours ago

    Meanwhile, my company has systems insisting on expiring ssh keys after 90 days…

    • dan@upvote.au
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 hours ago

      I’m surprised they’d expire the SSH keys rather than just requiring the password for the key to be rotated. I guess it’s not too bad if the key itself is automatically rotated.

      It would be more secure to have SSH keys that are stored on Yubikeys, though. Get the Yubikeys that check fingerprints (Yubikey Bio) if you’re extra paranoid.

    • TBi@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 hours ago

      My company blocked ssh keys in favour of password + 2FA. Honestly I don’t mind the 2FA since we use yubikeys, but wouldn’t ssh key + 2FA be better?

      • JasonDJ@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        56 minutes ago

        Just store your keys on the yubikey. Problem solved.

        Or use a smart card profile and go that route.

      • dan@upvote.au
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        3 hours ago

        We use keys + Yubikey 2FA (the long alphanumeric strings when you touch the Yubikey) at work, alhough they want to move all 2FA to Yubikey FIDO2/WebAuthn in the future since regular numeric/text 2FA codes are vulnerable to phishing. All our internal webapps already require FIDO2, as does our email (Microsoft 365).