Looks like a huge amount of security vendors are working to have a secure and open standard for passkey portability between platforms.
It is always good to see major collaboration in the security space like this considering the harsh opinions that users of some of these vendors have toward many of the others. I just wish apps and sites would stop making me login with username and password if passkeys are meant to replace that lol.
I don’t like that passkeys are portable, this kind of defeats the entire purpose. The way they were sold to me is the following: it’s 2 factors in one. The first is the actual device where the key lives, and the second, the user verification, like a pin, face scan, fingerprint etc. If it’s synced across the cloud, there’s no longer the first factor being the unique key on the unique device.
Granted, passkeys even without the first factor are still magnitudes better in terms of convenience and security compared to passwords, but it just disappoints me a little that there are no good options to save passkeys on my local device only, with no cloud sync.
If anyone knows of a local-only passkey manager app for android, as well as the same as a firefox extension, I’d love to know about it!
Admittedly, for some password managers, the passkeys are stored locally and are not accessible in the cloud unencrypted without the decryption keys that exist on devices you authorize.
This may still not make a difference for you though. For me, I consider passkeys, even stored in the cloud, to be enough for the vast majority, so I appreciate these vendors working to make passkeys more easy for the end user.
I agree and I still store my passkeys in proton pass, but that’s more because there’s no real option for storing them locally only. I really like passkeys and they make me optimistic about the future, it’s just that I think the way they should work is that each device should have a passkey registered to an account, so that the access can then be revoked if the device was compromised. And it’s even convenient in this way with the QR codes that you can use to temporarily share a passkey to then be able to add the new device.
That’s completely fair. Appreciate the discourse friend
I guess you’re better off buying a physical security key, which offers some guarantee that the keys cannot be exflitrated from the device.
I have one, but I use it as a second factor because it does not have a way of identifying me
Strange, my Yubikey allows me to authenticate using Passkeys just fine by entering the PIN that protects my stored credentials.
Yubikey supports pin protection, the newest one even have a fingerprint scanner.
Setup 1password with a physical security key might fix that issue somewhat.
If you don’t want to sync your credentials with a server, why are you using a server based credential manager?
For 2 reasons:
- I want to sync my credentials that cannot be made unique and revocable (ie passwords). I can have a single passkey per device, I cannot have a password per device for a same account. I also have to memorize a password, and I have hundreds that I may need to access while I am away and only have my phone.
- I use one because currently I have not found a convenient way to save local passkeys on Android and my Linux PC.
You can save local passkeys using a local keepass file and keepassXC. No cloud needed.
Why is the buzz around passkeys is back? I am seeing them way more often than they used to be. I think I have created passkeys for 2 apps and don’t even know how that worked, it such a breeze that almost felt it wasn’t secure lol.
In what ways the passkeys are different than authenticator apps?
Passkeys are meant to replace password-based login whereas TOTP apps are only meant as a 2FA method.
Convenience and security.
Authenticator apps are still vulnerable to phishing, passkeys are not.
With the ability to transfer passkeys, the attack vector phishing does not sound that far fetched. Tho i have not looked into the transfer process.
We will see i guess.
Idk, a SSH-Key is also transferrable, yet it’s still safe
And given that Passkeys are essentially specialized ssh-keys, I don’t see the Problem.
But I’d like to know it I’m wrong.
Why do you think SSH-Keys are safe against phishing? I mean it is unlikely, that someone will just send the key per mail or upload it somewhere since most ppl using SSH-Keys are more knowledgeable.
When you now get an easy one click solution to transfer Passkeys from one Cloud provider to another it will get easier to trick a user to do that. Scenario: You get a mail from Microsoft that there is a thread and that you need to transfer your keys to their cloud.
The thing is, that you only have to share public keys and never private ones. So you can only phish public keys…
The thing is, that you only have to share public keys and never private ones. So you can only phish public keys…
How would you sync or transfer a passkey across devices without transferring the private key?
That’s July question: the article even points that out. If previously the private key was in hardware, never exposed, but now it has to be available to software. Does it open any potential attacks?
Even if it is less secure, this is probably a good thing to prevent vendor lock-in. I know that’s one reason I rarely use passkeys
You share public keys when registering the passkey on a third party service, but for the portability of the keys to other password managers (what the article is about) the private ones do need to be transferred (that’s the whole point of making them portable).
I think the phishing concerns are about attackers using this new portability feature to get a user (via phishing / social engineering) to export/move their passkeys to the attacker’s store. The point is that portability shouldn’t be so user-friendly / transparent that it becomes exploitable.
That said, I don’t know if this new protocol makes things THAT easy to port (probably not?).
Well, they made it very secure with the transfer of passwords /s
It felt so strange having a CSV file with all my passwords and 2FA secrets in plain text in my downloads folder…
Imagine if would not have used a encrypted partition, my passwords may still be on that disk…
I have my passkeys in my keepass file in my private cloud since about 6month using strongbox on iOS and KeepassXC on Linux. Sadly, not many websites support passkeys on firefox for linux desktop yet… Hope this helps!
Lol, I’m a semi-noob and this sentence is really intimating.
Keepass is a style of encrypted file with a list of the passwords and the syntax is standardised. There are many apps/programs for any platform that offer pw management based on that file. I use keepassXC app on linux and strongbox on iOS since both of them are well integrated into the operating systems. On ios i use the webDav protocol to sync the keepass file on my server with strongbox app. On Linux I use nextcloud sync to mount my files on the server into linux and in keepassXC I have set it to automatically grab that keepass file on boot. Ah of course the keypass file is protected by a strong password, but this could as well be a hardware token like a yubikey. But if you have a yubikey, you just store your passkeys on that😂
Seems like people in the comments are misunderstaning the announcement entirely. This protocol is about import and export from password managers and not about having them synced between devices. It would prevent a lock in effect. This is a great development!
FIDO Alliance’s draft specifications – Credential Exchange Protocol (CXP) and Credential Exchange Format (CXF) – define a standard format for transferring credentials in a credential manager including passwords, passkeys and more to another provider in a manner that ensures transfer are not made in the clear and are secure by default.
Lock in effect of passkeys is just infuriating 😂good to see progress!
yay glorified, overcomplicated passwords!
i get hate for it but just use a password manager if you can’t juggle them?
I think it is quite the opposite for the end user. If apps/websites, begin to replace traditional password login with passkeys, this will be a measurable improvement for average consumers.
not really an improvement if you need extra software for it.
and cant just easily login.
In one sentence, you say, “just use a password manager”, on the next, “not really an improvement if you need extra software”. I’m not sure what argument you’re having, but neither one really addresses what this article is about.
This keeps the passkeys in the password manager (I use dashlane, it rocks, and synchronises the passkeys just like the passwords), but this new protocol allows you to change and export the passkeys to other password managers, preventing vendor lock in and allowing for transfer to another password manager.
Hope this clarifies things! And everyone should use a password manager of some kind; we should expect whatever site we’re using to be hacked, and the only way to be safe is to have a unique password per site.
password managers are optional though
Jesus fucking christ this is like listening to Jason from The Good Place try to argue a point about encryption.
just waiting for it to happen. many articles glowing it up, but only corporations proceeding with vendor lockin.
