this post was submitted on 26 Sep 2024
549 points (99.3% liked)

Technology

59287 readers
4210 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] TBi@lemmy.world 6 points 1 month ago (3 children)

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?

[–] jj4211@lemmy.world 2 points 1 month ago (1 children)

All well and good when ssh activity is anchored in a human doing interactive stuff, but not as helpful when there's a lot of headless automation that has to get from point a to point b.

[–] TBi@lemmy.world 3 points 1 month ago

Yep. All the headless automation broke…

[–] dan@upvote.au 1 points 1 month ago* (last edited 1 month 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).

[–] JasonDJ@lemmy.zip 1 points 1 month ago

Just store your keys on the yubikey. Problem solved.

Or use a smart card profile and go that route.