12 ms·
Passwordless Authentication on Github.com
- ezekg 3y agoHow is my Yubikey Nano both something I know, and something I have? It requires no input other than touching it (which anybody can do). No PIN, no prompt. To me, that's only something I have, not something I know. I saw a Yubikey listed in one of the screenshots as an active passkey, so I'm curious how it fulfills the two-factor requirement.
- 5e92cb50239222b 3y agoThe "relying party" (the website you're trying to authenticate to) can request the browser to perform user verification and refuse to proceed without it. You'll need to type in your PIN then (or scan the fingerprint, or perform some other type of verification dance, whatever is supported by your device). The RP can also request not to perform it, but IME Chromium asks for PIN anyway. Firefox is not so insistent. You can play with parameters here (look for advanced settings): https://webauthn.io https://webauthn.io https://webauthn.me/debugger https://webauthn.me/debugger
- ezekg 3y agoAh. I guess I wasn't up to speed on WebAuthn.
- halJordan 3y agoThe yubikey is only something you have. Github will require the browser to get the yubikey and additionally get device authentication (password/pin/biometric).
- WorldMaker 3y ago> It requires no input other than touching it (which anybody can do). To be fair, under the blandest definitions of "something that you know", "I know to push this button at the right time" is something that you know (have learned/trained, even). Just because it might be obvious or easily guessed doesn't mean it isn't "something that you know". Anybody can do it, but you know to do it. Most passwords are easily guessed, many PINs are even more easily guessed and have a tiny search space (10^4 = 10,000 combinations), most signatures are easily forged, most "security question" answers are trivially googleable if people answer them honestly and don't treat them as "phone passwords". (Similar on the "something I am" front: fingerprints are not as unique as people think, confusingly shift over time, and easily spoofed; same, sometimes worse, with "face prints". There are a lot of interesting criticisms out there of current biometric factors.) The goal of multi-factor authentication in general is that more factors are better, and that the "strength" of each individual factor can be relatively weaker because the strength of the combined multi-factor is often (not always) stronger than the sum of its parts. You can use weaker PINs (or single button presses) than previous passwords if you trust your other factors or the interaction between factors to more than make up for it. As usual, it is mostly up to your personal threat model if you think you need a stronger factor in place than "I know to push this button". There are Yubikey models where you can require a PIN input every time. There are other similar security keys with biometric unlocks (fingerprint readers). Similarly, too, it is sometimes just fine for someone to say, "based on what I believe my threat model to be and all my other active factors I'm fine with calling 'I know to push this button' as my most common 'something I know'."
- grrdotcloud 3y agoHere's what I want: I'm a remote worker. My house is more secure than most thanks to my proximity to bad guys. I have a yubi that I push that puts in 80% of my password. I type the rest. This saves me time, adds complexity required by corporate. Why can't I incorporate the key and Chrome password manage? My cell could be easily lost or compromised (cloned or stolen) so using it as a 2FA always feels silly.
- jamjamjamjamjam 3y agoI use a long pin on my yubikey
- 5e92cb50239222b 3y ago> You are using a browser or device that does not support passkeys. Yet again the supposedly open standard is compromised by terrible implementations. I already ranted about PayPal which has somehow managed to only support mobile devices and macOS: https://www.paypal.com/us/cshelp/article/what-are-paypal-passkeys-help997 https://www.paypal.com/us/cshelp/article/what-are-paypal-pas... I added passkey support to a couple of projects at $DAYJOB and they work just fine on Firefox or Chromium on Windows, Linux, or FreeBSD if you don't go out of your way to break them. WTF GitHub?
- deleted 3y ago[deleted]
- donmcronald 3y agoThis is a big shift away from user's having control and towards big tech and device manufacturers having control. A device that can do signing for authentication can also do signing for authorization and, since the keys can be stored in a TPM, there's nothing you can do about it. The authorization half of the plan is going to come after everyone has adopted it for authentication. I'm convinced the technology in play here is going to be used against users. Get ready for "authorized actions" in the applications you depend on.
- WorldMaker 3y agoEverything about Passkeys are open standards. Open-source implementations already exist. Third party choices for passkeys outside of device manufacturers are already available if you don't trust your device ecosystem. Passkeys only survive so long as the Big Three (Apple, Google, Microsoft) push them together for mainstream users and it is a lot to suggest that those three companies can get along long enough and agree generally enough to conspire against their user's interests. If they show signs of such a conspiracy, there are anti-trust laws to deal with that. (Plus, as I said, open source and third party alternatives already.) But if we want to talk specifics rather than hypotheticals: there actually is a FIDO standard somewhat close to what you are afraid will happen called "Device Attestation". This allows TPMs to attest (sign) that a given key came from a specific type of Device, or even in theory a specific Device. Enterprises want this because it is an asset management and additional layer of security tool to make sure only approved devices have access to corporate stuff. Microsoft and Google have implemented it to various degrees. Apple on the other hand has made it publicly clear that they don't like the privacy and user security implications of Device Attestations and just plain aren't supporting it in their Passkey implementation. I can't prove that there aren't conspiratorial things happening behind the scenes between the Big Three, but at least in these specifics you have public evidence (in both words and actions to date) from one of the Big Three that they care about the privacy of their users much more than they care about what enterprise customers demand and are going to publicly disagree with the other two companies in the Big Three about it. Again, I doubt I can prove to you that the conspiracy doesn't exist, but it is so entirely unlikely given what we've seen so far.
- 3y ago