Very mixed feelings on GitHub’s recent approaches to security. Tighter security measures are great, but deprecating password authentication on git operations seems obtuse to me. What if I want to push a change from a machine that’s not mine and doesn’t have my registered SSH key on it? I don’t have a Yubikey or anything similar nor do I intend to get one in the foreseeable future.
I’m with you on this. How on earth are one-off login events supposed to work? I want nothing about me logging on to be stored on that device or account other than, for example, the code I download. Maybe I’m missing something but the search I just did suggested connecting my phone via bluetooth, which is also not an option.
Maybe I’m misinterpreting something here, but wouldn’t that mean, I can’t just access my account if I lose my auth device? Am I supposed to always have a passkey device locked somewhere safe?
My understanding is that these passkeys can be securely synced - either via your device cloud (e.g. iCloud), or hopefully soon via your password manager. So not that different in terms of UX than current 2FA, but more secure in the backend.
I just tried this out with Github. My passkey lives in 1Password so it’s backed up and synced across devices. It also lets me sign in with normal MFA/TOTP if I don’t have the passkey, or use a recovery code. Incidentally @[email protected] this is working in Firefox now.
So, it’s just a password with a different name.
Seriously, what is the functional difference between this and stricter password requirements? I don’t see it.
Passkeys use a challenge/response protocol that doesn’t transmit any actual secrets. This makes them phishing resistant as you can’t just “type in your passkey secret” it gitnub .com
You’re supposed to have multiple devices (phone, tablet, laptop, desktop, etc) that all store your passkey securely (it can’t just be sitting on the SSD…). You’re also supposed to backup your passkey.
Yes, if you lose access to all your devices it could prove challenging to access GitHub… but that’s a pretty unlikely scenario and most people should be willing to pay the price (what self respecting programmer travels anywhere without two or three devices?)
You are also supposed to backup everything you have on GitHub elsewhere… so it shouldn’t be a total disaster if you lose access. It’d just be annoying. And presumably GitHub has some kind of recovery process for someone who’s lost access to an account? What if the repository maintainer dies? Someone else has to be able to take over.
On the other hand - if my bank required a passkey… then I’d probably switch banks. If all my stuff is stolen or destroyed, I still need access to my money. And if someone compromises my bank… well it’s just money. The stakes are far higher if a popular GitHub repository is compromised.
deleted by creator
For anyone else trying to get it to work on firefox, it doesn’t support passkeys yet but it’s on the roadmap. https://connect.mozilla.org/t5/ideas/support-webauthn-passkeys/idc-p/30123/highlight/true#M17028
Firefox does support Passkeys - it’s just incomplete - specifically some of the major key storage locations aren’t supported yet (and it depends what operating system you’re running Firefox on, since every OS has different options for secure key storage).
SQRL’s problem is it only focuses on the login component. It doesn’t really solve storage/backup/sync. All three have to be extremely easy to use otherwise any authentication system is a non-starter for the general public.
Passwords might not be secure, but they are user friendly (if you allow bad passwords). That ease of use cannot be taken away.
Excellent point. I’ve got exactly one SQRL login and even it was just to play with it. I never got as far as real world considerations. :)
