News for hackers. Stuff that matters.
Re:Google Introduces Passkey Authentication by Animats on Thursday May 04, 2023 @07:37PM (#35823552)
Questions:

1. If you are using this to authenticate a non-Google service, can Google cut off your access to that service?

2. If your Google account is terminated, do you still have access to non-Google services?

3. Does Google possess sufficient information to log into non-Google services as you?

4. In the event that any of the above happen, do you still have the right to sue Google?

Re:Google Introduces Passkey Authentication by prepend on Thursday May 04, 2023 @07:59PM (#35823721)
This is just for authenticating to google, right?
Re:Google Introduces Passkey Authentication by Nifty3929 on Thursday May 04, 2023 @11:00PM (#35824746)
Yes, but if you use the “Login with Google” function on many 3rd party websites, then what? If Google locks you out, can you get back into your account on the 3rd party website?

I think this is a great question, and that the answer depends on the 3rd party site.

Re:Google Introduces Passkey Authentication by theaiquestion on Thursday May 04, 2023 @11:50PM (#35825016)
> Yes, but if you use the “Login with Google” function on many 3rd party websites, then what?

AFAIK this part has nothing to do with passkey's and is an issue with OAUTH, and has been an issue for years.

Re:Google Introduces Passkey Authentication by tisc on Friday May 05, 2023 @02:01AM (#35825696)
> […] and is an issue with OAUTH

This issue is not caused by OAuth, but by offering authentication via a third party. If you allow visitors to authenticate via a third party, you implicitly trust that third party. If that third party decides to revoke your account, then the logical consequence is that you can no longer authenticate. There’s no solution for this problem imo, other than not allowing authentication via a third party.

It is the same as airlines; They want you to identify using a passport. If your country decides to revoke your passport, you cannot check-in. That’s not an issue, but a logical consequence of choices made.

Re:Google Introduces Passkey Authentication by Animats on Friday May 05, 2023 @02:57AM (#35826109)
The trouble is that you can, apparently, have only one trusted third party. You can't have a backup authentication service in case the trusted third party fails. That's what's needed.

I'd like to have a regulated entity such as a bank, or even the California DMV, as a backup authentication provider. They have legal obligations that Google does not.

Re:Google Introduces Passkey Authentication by judge2020 on Friday May 05, 2023 @10:27AM (#35829669)
You'd need a law saying that the California DMV or whoever must run an oauth service, and then you'd see people integrate it. As it stands, this isn't a thing because the California DMV and even banks aren't interested in being the populus' IDP.
Re:Google Introduces Passkey Authentication by Animats on Friday May 05, 2023 @02:29PM (#35833312)
Banks are into this. JP Morgan Chase uses OAuth2 for some services. It's more of an enterprise thing right now.[1]

[1] https://www.jpmorgan.com/technology/technology-blog/protecti...

Re:Google Introduces Passkey Authentication by trallnag on Friday May 05, 2023 @07:09AM (#35827707)
Yep. I think Google is once again trying to place itself as a gatekeeper. The vast majority of apps out there will never implement passkeys.
Re:Google Introduces Passkey Authentication by notatoad on Thursday May 04, 2023 @08:14PM (#35823839)
there's two things here, passkeys as a mechansim to sign into your google account, and passkeys in general. i'll assume you're asking about passkeys in general, even though the announcement here is passkeys to sign into your google account - passkeys as a general standard were introduced earlier this year.

1. no, it's a cryptographic key stored on your device. but also yes, because if you're using a passkey on a device you sign into using your google account, google can lock you out of that account and potentially that device. if that device is your only way of logging into a service, you'd be locked out of the service in the same way that losing or destroying the device would lock you out of the service. but authorizing multiple passkeys and adding backup authentication methods is encouraged, so for practical purposes the answer is no.

2. you should understand that passkeys are issued by your device or browser. so if you don't want to trust google, you can use a passkey issued by safari or iPhone instead of Chrome or Android. if you're using an apple-issued passkey to sign into some other service that isn't your google account, google has literally no involvement anywhere in that chain.

3. not according to the spec. the passkey is a certificate that gets stored on your device. your device shares a signature (not the certificate) with the service you're signing into to prove you have access to the certificate. but they're issuing you the cert through their proprietary software. if you don't trust google to not snag a copy of the passkey when they generate it for you, you should use passkeys generated by an issuer that you do trust. (in apple's implementations, passkeys are synced through iCloud, so the answer there is yes - apple does have your passkeys and could sign in to services as you if they wanted. google is not doing that.)

4. you'd have to read the ToS for yourself to figure out what you could sue google for. but the more relevant thing than legal recourse is that this scheme doesn't really give google any power they don't already have, and in many ways distributes power out to third-parties so you have to trust google less. apple's passkey implementation is leading google's. others will follow. this is about allowing you to use an open standard to authenticate with your google account.

Re:Google Introduces Passkey Authentication by devsda on Thursday May 04, 2023 @10:09PM (#35824509)
On point 1 if google decides to lock you out of its service, it generally doesn't stop at a single device but all other devices you own and associated accounts can also be impacted.

So, the solution here seems to be not just creating backup devices (using the same account) but diversify the platforms as well like use a mix of android, yubikey, ios and any other supported platforms.

Doubt many people would have the time and resources to do it correctly.

Re:Google Introduces Passkey Authentication by notatoad on Thursday May 04, 2023 @11:12PM (#35824805)
As long as one of the backup methods included in "the time and resources to do it correctly" includes signing in with a password like you always have, I'd guess that most people will have done that.
Re:Google Introduces Passkey Authentication by larusso on Friday May 05, 2023 @12:05AM (#35825094)
The fallback to a password in this case feels so wrong. I mean it’s like ssh with password prompt enabled. They let this open for the conversion phase and monitor how often a user with a passkey is still using the password. But the ultimate goal should be to get rid of username/password credentials. I’m still uncertain if this will ever happen though. Given the track record of giant corps to lock out users for various reasons.
Re:Google Introduces Passkey Authentication by xyzzy123 on Friday May 05, 2023 @12:12AM (#35825137)
Also, diversity means you trust all of the providers; from a security perspective it's worse.
Re:Google Introduces Passkey Authentication by stouset on Friday May 05, 2023 @12:18AM (#35825172)
No? Your private keys are still on your physical device which you own. The providers do not get your key material.

If your threat model includes “the manufacturer of the device I use to authenticate myself is actively working against me”, you are already completely lost.

Re:Google Introduces Passkey Authentication by xyzzy123 on Monday May 08, 2023 @07:36PM (#35868362)
In order to be usable, many providers will implement some kind of override to allow recovery workflows. The keys may never leave secure storage (tho again that is an implementation detail there is no guarantee), but how sure are you about the backend configuration that dictates which keys or methods are acceptable authenticators?

As a trivial example, it seems very likely that providers will implement one or more forms of backdoor to ensure that LEO can access your cloud resources.

Re:Google Introduces Passkey Authentication by handsclean on Thursday May 04, 2023 @10:09PM (#35824511)
So, if I understand correctly:

1. Google can lock you out, but it’s ok because 1% of users have a workaround,

2. You will lose access, but it’s ok because you won’t if you didn’t use this product,

3. Google can log in as you, but it’s ok because we should trust them not to, and

4. We’ve got no recourse, but it’s ok because we were probably helpless anyway?

Companies may get away with this for other products, but the bar is way higher for security products. There are real solutions, or at least ameliorations, and it’d be unsafe to use the product without ensuring they’re there.

Re:Google Introduces Passkey Authentication by danpalmer on Friday May 05, 2023 @12:04AM (#35825085)
Sorry, but I don't think you do understand correctly, and I mean that in an honest and non-judgemental way, I think you may have misunderstood what Passkeys are, and what this announcement is.

With this announcement, you can log into a Google account with a Passkey. That Passkey could be generated by anything implementing the spec – an iPhone, a browser, a home-grown Python script, whatever you want.

Google can still lock you out of your Google account whether you use a Passkey or not. If you use your Google account to sign in to other sites, Google can also therefore still prevent you from logging into those other sites, as they have been able to do before (I don't know if they do this as a matter of policy, but they theoretically can).

Passkeys do not change this.

The only potential place that Passkeys might change things is if you use a Passkey generated by a Google technology, like Android or Chrome. You could use those Passkeys for logging into anything, not just Google accounts. As these are tied to a device, I don't believe the Google account on that device affects them in any way. Google can't lock you out of your Android phone, and can't prevent you using Chrome, so can't prevent you using Passkeys in either of those systems.

Re:Google Introduces Passkey Authentication by eduction on Friday May 05, 2023 @12:54AM (#35825344)
Typical Google condescension.

I am extremely security savvy and have no friggin idea what you guys are on about. “Passkey?”

Is that the word you guys decided to make up to replace, for some reason, “security key,” which people already knew? I have several of those, along with various TOTP storage apps, and zero desire to learn whatever new crap Google is trying to swindle us with. You guys can pound sand with this passkey crap, I’m glad I moved everything off Google years ago.

Re:Google Introduces Passkey Authentication by sowbug on Friday May 05, 2023 @01:05AM (#35825406)
Who are you yelling at? Passkeys are a FIDO thing. Everyone who has implemented them uses the same name. Apple calls them passkeys. Microsoft calls them passkeys. PayPal calls them passkeys. But if you're mad because Google also calls them passkeys, then... OK.

(I'm also having trouble squaring "extremely security savvy" with the question whether a security key is a passkey... but OK.)

Re:Google Introduces Passkey Authentication by danpalmer on Friday May 05, 2023 @02:53AM (#35826073)
I'm sorry you don't appear to be interested in engaging with the topic. Even a cursory look would reveal that this is a new open standard spearheaded by a cross-industry group.

I'm hoping Passkeys do indeed take off as they provide better security for pretty much everyone, and if they do your service providers will most likely adopt them.

Re:Google Introduces Passkey Authentication by seanhunter on Friday May 05, 2023 @02:38PM (#35833447)
I am no fan of google, but this is such a grotesque distortion that it feels like you are just pushing an agenda here.

1. They can lock you out of your google account and services you authenticate using login with google, but no more or less than they can lock you out without passkey authentication.

2. You may lose access as per #1, but no differently than if you lost access to your google account having used MFA or whatever other method to log in. It's completely orthogonal.

3. This is just wrong. The passkey is a cert which is used to sign something and send them the signature they can verify with the public part of the cert. They can't login as you. If you don't trust them not to backdoor the passkey itself during generation you can use a passkey generated by someone else.

4. You never had any recourse. This doesn't change that at all either way. It's a login methodology.

Re:Google Introduces Passkey Authentication by js2 on Friday May 05, 2023 @01:13AM (#35825440)
> (in apple's implementations, passkeys are synced through iCloud, so the answer there is yes - apple does have your passkeys and could sign in to services as you if they wanted. google is not doing that.)

Passkeys are stored in the iCloud Keychain which is end-to-end encrypted with 256-bit AES. Passkeys cannot be read by Apple anywhere but on your own device.

Re:Google Introduces Passkey Authentication by 5ersi on Friday May 05, 2023 @01:34AM (#35825551)
So how does a new device join your iCloud and sync Keychain?
Re:Google Introduces Passkey Authentication by dan-c-underwood on Friday May 05, 2023 @01:42AM (#35825594)
Re:Google Introduces Passkey Authentication by starfallg on Friday May 05, 2023 @02:07AM (#35825728)
Apple can install any software it wants up to the bootloader (iBoot) level on your iPhone via updates. So technically they can access your keys.
Re:Google Introduces Passkey Authentication by j16sdiz on Friday May 05, 2023 @05:19AM (#35826965)
Yes. So do any OS/TPM vendors.

Unless you control/audit the whole stack (and forbid updates), you have to trust somebody.

Re:Google Introduces Passkey Authentication by judge2020 on Friday May 05, 2023 @10:25AM (#35829644)
You can reset your device using an IPSW you got off the internet if you want to make sure Apple isn't shipping targeted firmware to your device specifically.
Re:Google Introduces Passkey Authentication by js2 on Friday May 05, 2023 @11:25AM (#35830458)
I anticipated this reply which is why I added the qualifier "anywhere but on your own device." Unless you intend to manufacture your own device from scratch, at some point you have to place your trust somewhere. See "reflections on trusting trust":

https://web.stanford.edu/class/cs208e/cgi-bin/main.cgi/stati...

Re:Google Introduces Passkey Authentication by notatoad on Friday May 05, 2023 @07:10PM (#35836242)
Does icloud e2e still have a loophole where apple can re-key it for you whenever they want? That's how it used to work, and as long as that's how it works their e2e is just for show.
Re:Google Introduces Passkey Authentication by judge2020 on Friday May 05, 2023 @10:24AM (#35829633)
> (in apple's implementations, passkeys are synced through iCloud, so the answer there is yes - apple does have your passkeys and could sign in to services as you if they wanted. google is not doing that.)

iCloud Keychain is e2ee.