timmyc123

iCloud Keychain is required on macOS to create passkeys in Apple Passwords (which uses iCloud Keychain to securely sync them). Apple Passwords is the default credential manager in macOS (similar to Google Password Manager on most Android devices). If you want to save to another credential manager (app) on your Mac, you need to install it and enable it. If you don't have another credential manager on your Mac, that is why you can't save a passkey on your Mac and are given the option to save to another device.

You can. Choose a credential manager that offers that feature.

I just don't think that's a good idea for most users. Imagine an older relative being coaxed into exporting all their passkeys in plaintext and uploading them to a website.

> It's notable that several of the claims on that page conflict with the other info in both the OP article and the follow-on.

Create GH issues or use the feedback form if you believe there are issues with the content!

AAGUIDs are not unique to authenticators. Hundreds of millions of people using the same product have the same AAGUID.

maybe read the whole issue?

Microsoft Entra is a workforce product. An employer always decides how you authenticate to your work account. It's not your account.

Lot's of additional great information for consumers and prosumers at whatarepasskeys.info. Many of the questions that are constantly discussed in these comments are answered in the FAQ and content.

Contributions and feedback are welcome! GitHub link is at the bottom of the page.

The primary reason 2FA exists is because passwords are phishable. If you remove passwords, the need for 2FA largely disappears.

Asking that services require you to encrypt your backup file by default to protect against local malware or malicious access is certainly not "The people behind passkeys do not like...allowing you to export your passkeys".

Hey Hacker News! Over the past few years, most posts about passkeys have spiraled into endless debates with hundreds (and in some cases thousands) of comments. I've ventured into many of these trying to provide some context from the development of passkeys and some ecosystem perspectives. Two big observations were that there aren't any vendor neutral resources for regular users to help understand passkeys, and many sites/apps which use passkeys don't provide a lot of guidance or education to users.

A few of us from the passkey developer community have teamed up to create a new consumer-friendly site about passkeys, with easy to understand explanations and illustrations, frequently asked questions, and some details on picking a good credential manager. There's also an advanced toggle which adds some technical details to each section (and in the future some more technical FAQs and sections). Much of the content is based on questions and comments from this community as well as Bluesky, the Fediverse, Reddit, and direct user engagement.

The goal is for this to be a living site, with constant tweaks based on community feedback. You can create issues and/or PRs on GitHub or just submit general feedback via the web form (both are linked at the bottom of the site). The site has no corporate backing or influence, and all feedback is welcome. Scathing critiques or praise. Just please be respectful.

We're also eagerly looking for non-native English speakers to review translations for the current future localized versions of the site.

If you run a site that offers passkeys, please consider adding a link to your docs, and even your passkey enrollment screens.