
Follow ZDNET: Add us as a favorite source On Google.
Key takeaways of zdnet
- Adopting passkeys is fragmented in sites and equipment.
- Users still require passwords for recovery and new device setup.
- Despite the phishing protection confusion, it is worth connecting.
Ok. Good. I have finally decided to embrace Paske. But why does it feel so ick?
As you probably know, the technical industry is replied for the problem of passkeys password. Unlike password data, which can be breeted, fish can be done, quish, Q., visited, and scared, passkeys require an encrypted private key that you have only (at least theoretically).
They are the summit of modern credential safety, and we should all use them. Or at least, this message is that our favorite sites are constantly disturbing us.
But not so much. The reality is the way, Via This should be compared to messier.
I’m going to passkeys
Slow, bako. You do not clearly step For passkeys. Most of the time you add them. Stay here with me. I am trying to declare some promotions and shares my understanding that this overraching Beasty is fit in our Credit Security Infrastructure.
Let’s start with me recently with a small digital adventure.
I decided to give recently after several times I was ignored several times by many sites used daily. I decided to “move” in Paske. At the point, I mistakenly believed that Pasakies are replacement for the user name/password paradigm we have been using for decades.
Also: What are Pasaki? How to go to password free can simplify your life in 2025
Indeed, about two years ago, I summarized Pasakies, only to leave them almost immediately. It was the same as they were adopting quickly, and I, as a professional early adoption, I thought I should jump on Bandwagan. The experience was a complex mess. I quickly left the effort.
Now, however, that effort has been a few years. My sites have started harassing me continuously about Paski. I thought that most of my first, the most worst challenges since sick efforts have gone away. Certainly, so many consumer-support sites push the muggles to use passki, technology must be ready for primetime.
I started with a famous financial institution. My previous login method was the user name and password, combined with my certification app for second factor authentication.
Following the instructions of the site, I applied the passkey login. The process went quite smoothly. Within a few minutes, I was able to log in with my pass.
At that point, I decided to remove the certification key from my authentic app, as I upgraded to Paski and no longer an authentic code would be required. After all, a part of the reason for upgrading to Paski is to finish the extra work on the login, right?
But then I tried to log in again. I was not closed. Instead, I was presented with my password or my logging choice. Out of curiosity, I tried to log in with my user name and password. that worked. But, of course, I was not asked to certify, because I had changed that important security facility a few moments ago.
Also: How do I easily set passes through my password manager – and why you should also do it
Huh. Ok. The financial institution had allowed me to remove the authentication method, but apparently my user name and passwords were still connected to my account. No amount of digging around in settings will not allow me to remove my password and go to all the dasters.
Surprised and quite angry, I went back to my account, enabled the authentic key again, and surprised why I am also upset with Passki.
Dull a friend
The game show who wants to be a Millionaire? There is a feature called “Phone a Friend”. The idea is that if a contestant is asked a question that is very difficult to answer, then the player gets to call a friend for advice.
Also: How PassKeys Work: The Complete Guide to Your Unnecessary Passwordless Future
One of my favorite aspects of working with ZDNET is that I work daily with some of the best informed subject experts in technology. So I decided to let my resident Pasti expert, David Burlind dull. He has written a full range on Pasakies that I consider using compulsory reading and using online for anyone living in the 21st century.
Burlind was enough to jump on a slack voice chat and spent about an hour with me, stating how Pasaki actually works.
It turns out that passKeys is such a mess because each site applies them differently. Each site you certified are called “Riling Party” in Pasaki Speak. Passkeys itself is a surname for fido2 credentials. By the way, if I find something wrong here, it is not the fault of Burlind. I am missing whatever I tell me from my notes, which can be the implementation of the passak of the industry as well.
so. Each site applies them in a different way and is applying a separate “transition path” from password to password to password. Some sites will only allow you to log in with Passke. Some let you switch to the password on the password. And some, like the financial institution above, keep both.
Also: 10 Pasaki Survival Tips: Now prepare for your passwordless future
Another bizarreness is that some sites allow you to use the same pass on all your devices. Other, especially PayPal, you need to install a separate passky on each device. These are called “device-bound passkeys”. If you use your Mac Studio, your MacBook Air and PayPal from your iPhone, you will need three different passes.
Now, here is where you are going to get brain freeze.
PayPal requires device-bound passkease, which they are probably to be additional hardworking about your safety. But think about it. If you add a passki to your MacBook Air and remove the password access, how are you going to add a new device-bound pass in your Mac Studio and iPhone?
Also: How to set and use passkeys in your iPhone, iPad and Mac
Yes, you have to log in with your user name and password, then set the passki for the new device. But since you almost always need an option to add a new device (eg, for example, if you upgrade your iPhone this fall), you always need a user name and password access for PayPal.
It seems to defeat the purpose of the passki, which is better, more secure and to give less violations of authentication.
When I introduced this contradiction for Berlind, he had some sage advice.
ZDNET recommendations
Just out of sick curiosity, I asked the chat, “Why do you suck passkease?” It replied:
Passkeys are not necessarily “sucking”-they are far more secure than passwords-but they feel broken in behavior due to the ecosystem lock-in, poor cross-platform purpose and confusing recovery processes. They will probably get better because adoption increases and workflow matures.
(Disclosure: ZDNET’s original company Ziff Davis filed a case of April 2025 against Openai, alleging that it violates Ziff Davis copyright training and operating its AI system.)
This tracks it with what I have learned from Berlin. He told me that he uses Pasaki for any relying party that provides them. Beyond the easy login for those sites, they had an interesting reason: protection from fishing.
Also: Why the road from password to Pasches is long, rugged, and it is worth it – perhaps
He said that if he descends on a site where he knows that he uses the passke, and the site asks him to log in with his user name and password, then that site can actually be a fake. Passkey request, essentially, is a verification system that you are on the site you intend to be. This is because scammers cannot harvest the passkease. Okay, they can, but due to private key encryption, whatever they harvest will not be usable.
Therefore, using passKeys can help you install a statusal awareness trap for fishing efforts.
For me, I have decided that if a site provides passki authentication, I am going to add it. If nothing else, it will prevent sites like Amazon from constantly harassing me. But it will also provide that the Fishing Awareness Protection Burlind recommended, and bring me into the practice of using and tolerating the passke.
I think I would suggest you to do so. Keep track of your existing user names and passwords. Make sure that wherever you can, set the multiproor authentication, and keep the track of those recovery codes. But also add safety, authentication and infection preparation to the Pasakies as a belt-endsers level.
Also: I replaced my Microsoft account password with a passkey – and you should also
be careful. The false sense of safety provided by passkeys can take you thinking that you are preserved when you are not. Do not implement passkeys thinking that you can remove other factor authentication protection. Keep in mind that the task of implementing the passki will not directly increase your account security if there is still a user name and password system. You should still use other factor authentication for accounts that provide it. They are presenting it for a good reason.
It seems that as long as you protect your user name and password, the way we all have been trained, adding the passki to the mixture does not hurt anything. It simply makes it simple to sign in. It is very clear that this is the future method. I just want it to be such a dirty, firm, incompatible, misleading future. But this is progress, right? Correct?
Have you started using passkeys so far, or are you sticking with traditional passwords? Do you find mixed implementation on misleading sites, or do you see clear benefits in fishing safety? How do you balance the facility with safety in your own accounts? Let us know in the comments below.
You can follow my day-to-day project updates on social media. Be sure to subscribe to My weekly update newsletterAnd follow me on Twitter/X @DavidgewirtzOn Facebook Facebook.com/davidgewirtzOn Instagram Instagram.com/davidgewirtzOn blue @Davidgewirtz.comAnd on youtube Youtube.com/davidgewirtztv,