this post was submitted on 26 Apr 2024
38 points (95.2% liked)

Cybersecurity

5610 readers
171 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Community Rules

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !cybersecurity@lemmy.capebreton.social !securitynews@infosec.pub !netsec@links.hackliberty.org !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 1 year ago
MODERATORS
top 3 comments
sorted by: hot top controversial new old
[–] Illogicalbit@lemmy.world 18 points 6 months ago (1 children)

A good read and a validation that it’s frequently a good idea to approach new security technologies with caution. The new hotness isn’t always the best thing.

[–] sugar_in_your_tea@sh.itjust.works 17 points 6 months ago

Honestly, when I saw "passkeys," my first thought was "vendor lockin." Google and GitHub did it with SSO using OAuth, and they're doing it again with passkeys.

Honestly, this is a "surprised Pikachu" moment for me. The closer you get to convenience, the more the big players will want to lock you in:

  • biometrics
  • voice recognition
  • passkeys

Passwords are hard to lock down because it's easy to switch to something else.

[–] 4grams@awful.systems 14 points 6 months ago

I love the promise of passkeys but it’s been painfully obvious the promises are just wallpaper over the actual intent which is vendor lockin.