12 ms·
The biggest issue with passkeys is that I just can't trust the companies offering them. They are locked into the platform for reasons that are ostensibly securi
by saagarjha 3y ago
The biggest issue with passkeys is that I just can't trust the companies offering them. They are locked into the platform for reasons that are ostensibly security but often indistinguishable from platform lock-in. If you make a passkey on an Apple device as far as I can tell it will never leave that device, ever, and there is no way to change this. Of course this means you can never be phished for your credentials but if Apple decides to delete your key or you want to leave your iPhone behind, what are you supposed to do?
- tjoff 3y agoThis is alone a big enough reason that there never has been any reason to be hyped about passkeys. The hype train on passkeys has been insane.
- gehsty 3y agoI thought passkeys were shared across Apple keychain (like passwords?) so you make a passkey on iPhone your iPad can use it.
- vbezhenar 3y agoYes, that's correct, they're stored in Keychain and shared using iCloud.
- saagarjha 3y agoAh, yes, poor choice of words on my part. They are in iCloud Keychain (I think this is required?). But if you only have one device it's basically the same thing, or if you're trying to leave the ecosystem.
- whereismyacc 3y agoAre they not private keys that shouldn't be synced across devices? I thought icloud facilitated automatic creation of passkeys for each device, not actually sharing the same passkey across devices?
- landmass 3y agoThere are two types of passkeys (1) resident, hardware-bound, non-copyable, installed on Yubikey etc., and (2) non-resident, copyable. Technically, by not being copyable, a resident key isn't a "Passkey," but that's just terminology and it serves the same purpose as a passkey.
- FireBeyond 3y agoThat's the crux of one of the debates... members of the FIDO Consortium threatening KeePassXC and other open source tools with blocking for sharing "roaming keys", meanwhile "Oh, Apple wants to share keys via AirDrop? No problem", which is one of the concerns, that it's yet another "push users to Apple and Google's tool of choice".
- sevanteri 3y agoThis is why services need to support multiple passkeys per user just like they should support multiple 2FA methods...
- Nextgrid 3y agoBig problem with this is that enrolling the secondary passkey requires the authenticator to be present. This is super inconvenient and risky as it always requires both authenticators to be present at the same machine/physical location, exposing both to local, physical threats (faulty USB ports on your machine frying anything you plug in? Congrats, you've now fried your main and any backup authenticators before you realized what was happening). Ideally, you should be able to get an authenticator's public key and be able to enroll one without presenting the authenticator itself, allowing you to keep it in a safe/etc. This would enable an easy workflow - enroll main authenticator as normal, then enroll your safely-stored backup by pasting its public key. If you lose your main, go to your safe, get your backup and "promote" it to primary and enroll a new backup one which goes in the safe.
- 4ad 3y agoThis is why you need to enrol the secondary passkey at the same time you enrol the first one, not later when you might not have the authenticator present. In reality websites should not allow setting up a single passkey.
- cuu508 3y agoEnrolling both at the same time still requires both authenticators to be present at the same machine/physical location.
- e12e 3y agoProblem remains when you lose one, and need to block and enroll a new backup?
- radicality 3y agoApple actually forces you to use 2 keys when setting up security keys for iCloud, just did the setup few weeks ago.
- advael 3y agoHonestly platform-locking has so frequently and consistently been the intent of security-washing rhetoric and major breaches have become so commonplace that I now view "security" in the press to be a euphemism for lock-in first and foremost, with other usages being anachronistic or niche
- lynx23 3y agoDont forget the euphemism "For your security" == "surveillance" -> EDR
- dimitar 3y agoUse a different factor of authentication and setup a new passkey?
- red_trumpet 3y agoDo you have to do this for every account? Like changing my password on every account?
- dimitar 3y agoyeah, I agree this is not a good experience
- cassianoleal 3y agoI agree. So far I think KeePassXC is the only one that allows you to export your Passkeys. I believe Bitwarden are working on it as well. That said, it's unclear whether this will provide any portability of passkeys between providers.
- Tempest1981 3y agoOnce you export your passkeys, is there anything that can import them?
- cassianoleal 3y agoI assume each provider will have the ability to import as well as export. The question is whether you can do that across providers. That's not too different from the status quo for passwords and other fields though.
- jasonjayr 3y ago... and they are getting warned about that feature existing: https://news.ycombinator.com/item?id=39698502 https://news.ycombinator.com/item?id=39698502
- diggernet 3y agowith an excellent response to that warning here: https://news.ycombinator.com/item?id=39706876 https://news.ycombinator.com/item?id=39706876
- jasonjayr 3y agoYep, I agree with that response completely. That whole thread is a great read about the reality of the passkey situation, and what it will take to really make it great.
- fbdab103 3y agoThe entire passkey situation is pretty telling that the spec was created with just vague promises that export would be handled at a later date.
- madeofpalk 3y agoI think it is true that you can's export passkeys stored in Apple Keychain. However, the statement is false in two ways: - Apple's iCloud Keychain syncs across devices - Apple has APIs that allow third party apps to create and offer passkeys, presented as a first-class option in Apple's authentication system. I use this to sync my passkeys between my Mac, Windows PC, and iPhone.
- ajsnigrutin 3y ago> - Apple's iCloud Keychain syncs across devices ...as long as you always keep buying apple.
- kiwijamo 3y agoHow do you sync it to your Windows PC? Is it native Apple-Microsoft sync or does it require e.g. installing an Apple application?
- bitlevel 3y agoI would also like to know how this is achieved.
- tssva 3y agoApple’s iCloud for Windows includes an iCloud Password app which allows accessing and managing your keychain stored passwords on Windows. They also have a browser extension for Chrome and Edge which does autofilling in those browsers on Windows. I haven’t used them in a long time so I don’t know if they have added passkey support to them yet.
- lo0dot0 3y agoHow do you sync to an Android phone?
- tssva 3y agoI don't sync anywhere because I don't use the Apple keychain for my passwords. No idea if there is a solution for Android but the original claim was syncing between your devices was only possible if you stayed strictly with the Apple ecosystem. This is not accurate since you can sync to Windows even if you can't sync to Android.
- Tomte 3y agoEnroll another passkey. Password manager can also do that (Bitwarden, for example), so I really don‘t see a reason for all the agitation.
- tsimionescu 3y agoBecause there is no way to do that at scale. If I've tied 200 services to my Windows-managed passkeys and now I want to switch to Linux, I have to manually go to each of the 200 services and ask them nicely to allow me to enroll a second key. This is simply unacceptable - and it's not like I could have done this ahead of time when I first signed up.
- pricechild 3y agoBitwarden (& vaultwarden) also offer passkey which seem to work pretty well. I've not had a problem registering both this and my phone on any site.
- kiwijamo 3y agoI've found the Bitwarden to be hit and miss. Some sites work fine with it, others don't work. I haven't debugged it enough to work out whether the problem is on the Bitwarden end or the website end or something else altogether. Given I'm wary of the benefits (or lack of) of passkeys I haven't really looked into it in depth as I have other 2FAs I can use instead.
- michaelt 3y agoIf you've already got a password manager, what benefit do you get from passkeys? Avoiding the risks of short, weak passwords? The risks of reusing passwords across sites? The inconvenience of remembering loads of passwords? The frustration of having to type passwords manually? The risk of getting phished or typing one site's password into a different site? Remembering and typing usernames? The password manager takes care of all that for you already. And if your objective is to have a second factor just in case your password manager gets compromised? A physical button just in case someone takes over your mouse and keyboard? Or a credential stored in a secure element that's (somewhat) protected even if you use it on a compromised machine? Putting it in a password manager (or OS keyring) removes those advantages.
- mid-kid 3y agoAutomation. Password managers should be the default authentication method, and the current hack of having it type text into a password field is both unwieldy and completely avoidable.
- posix_monad 3y agoVery easy to put the a password into the wrong place when doing it manually.
- 3y ago
- deleted 3y ago[deleted]
- bradley13 3y agoKeepassXC says that it is adding (has added) passkey support. I haven't tested this yet, but if it works, that would avoid platform lock-in. Assuming, of course, that the platforms don't somehow intercept the passkey requests and refuse to allow KeepassXC to do its job. The big tech companies (Google, Apple, MS) have all become evil.
- bonton89 3y ago> Assuming, of course, that the platforms don't somehow intercept the passkey requests and refuse to allow KeepassXC to do its job. My understanding is the ability to do that is built directly into the spec with the attestation feature. The only thing that might slow it down is Apple choosing to not implement it and zero out their device string. Others can piggy back on that to protect themselves behind Apple's skirt, at least until Apple changes their stance anyway. Platforms of course could just not allow Apple passkeys and only allow Apple users to use other 2FA options as well. Rest assured that small players like KeepassXC will be the first ones to have their passkeys blocked or not supported. The whole thing is a trap IMO.
- frantathefranta 3y agoI've tried it and it works on GitHub. Sites seem to be hit-or-miss for now. Tip if you want to use it with the browser add-on, it needs to be manually enabled and you also need to remove any YubiKeys from the system because it will prioritize them over KeePassXC
- sigzero 3y agoI like that app but until they add in templates, it's a no go for me. They are discussing it though (for 2.8.0), so maybe a future thing. https://github.com/keepassxreboot/keepassxc/issues/8228 https://github.com/keepassxreboot/keepassxc/issues/8228
- stavros 3y agoStore your passkeys in BitWarden.
- JTyQZSnP3cQGa8B 3y agoI love Bitwarden but they still don’t support that on mobile phones.
- JaneLovesDotNet 3y agoI think it's very close to landing into the release version. I've seen people discuss it working in the testflight/beta release on iOS
- Repulsion9513 3y agoBecause if you don't want to, it'll get in your way every time you try to use your actual passkey. Oh right, I forgot they added an option - now it just gets in your way every time you try to use your actual passkey on a new device.
- troupo 3y ago> The biggest issue with passkeys is that I just can't trust the companies offering them. They are locked into the platform for reasons that are ostensibly security but often indistinguishable from platform lock-in. On MacOS you cannot enable passkeys (or using TouchID with them?) without enabling iCloud Keychain. I'm fine with iCloud Keychain. But to enable it, you have to enable "autofill form password" which enables it in Safari. Disabling it in Safari disables the global setting and disables iCloud Keychain. WTF. https://twitter.com/dmitriid/status/1782787035637375050 https://twitter.com/dmitriid/status/1782787035637375050
- triblemaster 3y agoYou can always use passkeys like Yubikey or others which are much more multi-platform.
- crote 3y agoThis isn't a viable option in practice, because Passkeys use "Resident Keys". This means the credential needs to be stored on the Yubikey - which has a limited number of key slots. Need to log in to more than 25 (I believe) websites? Tough luck!
- AlexandrB 3y agoIt didn't have to be this way, but the hype train won over practical considerations: https://fy.blackhats.net.au/blog/2023-02-02-how-hype-will-turn-your-security-key-into-junk/ https://fy.blackhats.net.au/blog/2023-02-02-how-hype-will-tu...
- orbisvicis 3y agoWhy couldn't a non-resident security key send it's public key as username? And the response contains the actual username and private key.
- Repulsion9513 3y agoPrivacy. The idea, IIRC, was to have separate identifying material for each site.
- crote 3y agoBecause the security key doesn't store any public keys. Basically, the security key stores a single symmetric key. It'll generate a public/private keypair on registration, encrypt it, and send it to the server. On authentication the server will return the keypair back to the security key, which decrypts it and uses the retrieved private key for authentication.
- navigate8310 3y ago
- whywhywhywhy 3y agoThe platform lock in attempt is wild, my initial experiences with Passkeys were great on iOS and Safari, either getting pushed to touch-id or scanning a QR with my phone. But then in Chrome I couldn't get into GitHub because chrome would only push me to use their manager and wouldn't offer a QR code. Seeing this more and more with Chrome, like Credit Card numbers used to just save and autocomplete in browser but then they had some popup that was worded in a weird way that tricked me into saying it into Google Pay. Then I had to like type in the CCV to retrieve the card but then it also charged my bank account 1c for the privilege of autocompleting the card each time. Took me good 20 minutes to delete my card, get it saved back in the free local auto completely and shut down my Google Pay account I never knew I had.
- Groxx 3y agoYep, this is why I don't use passkeys. I tried. The power-grabbing garbage was immediately apparent and sent me straight for "heck no, I'll just use passwords until they figure this out, at least that can't control my password manager". In principle I should be very in favor of them, but the wild variety of lack of support for basics, and the built-in-the-spec ability for site X to control how I store and sync stuff is utterly bonkers. It's feeling like the OpenID promise -> OAuth platform lock-in cycle all over again, but compressed into v1.
- sroussey 3y agoI use 1Password which supports Passkeys, and don’t have an issue across mobile or desktop. I don’t get what the issues people have really are. I never experience them (fortunately!).
- MrDrMcCoy 3y ago1Password is a closed-source, cloud-hosted service. At any time, for any reason, they can close and delete your account, leaving you high and dry. Self-hosted, multi-device password managers are the only real solution. Thankfully, Vaultwarden and KeePassXC fill this role perfectly. Now if we could just get the other providers that require insecure email/SMS 2FA to follow suit, that would be great...
- lapcat 3y ago> If you make a passkey on an Apple device as far as I can tell it will never leave that device, ever, and there is no way to change this. That's not true. Passkeys actually require iCloud Keychain, which is obnoxious, because you can't use the OS passkey support without using iCloud. And you can't even manually export passkeys from iCloud Keychain, which is totally opaque. So it is still platform lock-in, just not in the way you described.
- xcrunner529 3y agoSo use a password manager still (1P). You can have multiple passkeys for different devices or keychains but no entering passwords or credentials. Still an improvement and far less vulnerable.
- lapcat 3y ago1Password is a platform, one that has gotten worse over the years. They've taken a bunch of venture capital, switched to rental pricing, and apparently now demand that everything be in the "cloud". No thanks. I prefer to be my own password manager.
- xcrunner529 3y agoI was just giving an example.
- moscoe 3y agoThen perhaps Bitwarden… or do you have a bone to pick with them as well? There are choices.
- maeil 3y agoUsing a good old password means you don't rely on any particular service, period. Passkeys means you do, you rely on either a particular type of device (e.g. Apple device) or a SaaS. It doesn't matter how many SaaSes offer it or how many brands of devices adopt it. It still means that for access to all of your accounts, you either 1. Have to stay with that brand of device or 2. Have to rely on the goodwill of the SaaS not to suddenly start raising their prices (the comparison here is passwords, which are free). Before you say that switching providers is possible, that doesn't really matter. Let's say I stored the passkeys on my iPhone/iCloud. And then it got stolen.. whoops! Now I must at the very least acquire another Apple device until I can reach any of my accounts, i.e. I'm tech-dead until I do so. If switching is not frictionless, it's an absurd level of lock-in, almost making it impossible. I have to go into every single account and add a new passkey? What if I forget one when I switch, then I'm out of luck and can never use the account again?
- teeray 3y agoThis is why I’m not interested in passkeys unless I can use it with my password manager (which I probably can at this point). It would also be nice to see the spec for these specifically address lock-in and provide anti-lock-in measures.
- tomschlick 3y agoNot sure what your password manager is, but 1Password supports them and its a pretty smooth experience.
- frantathefranta 3y agoKeePassXC has support for passkeys now. However I've only managed to make it work with GitHub. Bitwarden does not work for now (although their passkey implementation for log-in is reportedly in beta).
- Double_a_92 3y agoThe idea of a passkey is that it's bound to a device, and you can have more than one passkey. Think of a YubiKey, just that you can use your Phone or your PC instead. You basically have designated hardware that is always allowed to just login to your account...
- fbdab103 3y agoThen why can it be backed up to the cloud?
- aednichols 3y agoMy passkeys are in 1Password and work on every new device I set up.
- troyvit 3y agoI've had a link to OnlyKey's user guide bookmarked for about a year[1]. They're an open hardware company that offers a key. Despite that I still can't be bothered to go through with it. The article we're talking about includes many of the reasons. I feel bad for the author. They put a lot of their heart into something that could have been awesome. [1] https://docs.onlykey.io/usersguide.html https://docs.onlykey.io/usersguide.html
- Repulsion9513 3y agoGo buy a Yubikey?
- Double_a_92 3y agoAs I understood it, that's exactly the purpose and not an issue. You are supposed to create a new passkey on each device you have. The fact that they can roam around within e.g. the Apple ecosystem is just some added function that Apple offers.
- al_borland 3y agoIf I first signup for a service on my iPhone, then want to login on a Linux desktop, for example, how would I login if the passkey is not on my system, and I can’t login on the desktop to say I’m me? Maybe they sorted all this out so it “just works”, but there seems to be so many potential pitfalls, that I feel like I’d need to spend weeks researching stuff and testing edge cases before I could feel safe using it. No one is going to do that. With a password, I know it works now, and it will work in 40 years. I don’t have that same kind of confidence with a passkey. Even if it’s great, if people don’t adopt it in mass, it will fade away and be removed, so how deep do I want to go? This isn’t something I want to be an early adopter on, at least not for anything I care about.
- int_19h 3y agoYou get a link (or more commonly a QR code) that you open from the device on which you already have the passkey to grant access to the new device. Then you add the passkey for the new device. FWIW I don't think that this makes passwords redundant in general, but with passkeys, password becomes a last-ditch safety valve to regain access to the account. Meaning that it can be generated, very long, and stored in a way that is optimized for safety and security over ease of access (like, say, an encrypted text file on multiple USB sticks stored in different physical locations).
- vbezhenar 3y agoOne big issue with this QR thing is that phone will need to talk via bluetooth to the PC. Like every PC comes equipped with bluetooth chip. Should be some kind of pin code instead.
- sheepscreek 3y agoThere is a way around this. Password managers. I use 1Passwords and it acts as the vault for all my Passkeys. Can access them on all devices. Super happy with it.
- Pfhortune 3y agoIs there a way to export a passkey from 1P to use in a different manager? (Legitimately asking, I haven't tried passkeys yet due to portability concerns, and this would be good to know)
- pkzip 3y agoIf you want portability, then you can use HW security keys that support passkeys.
- ceinewydd 3y agoNot currently. Someone already did lots of research on this — https://community.bitwarden.com/t/passkey-portability/59177 https://community.bitwarden.com/t/passkey-portability/59177 There’s some hope for interoperability between password managers someday. There doesn’t seem to be agreement on how you can securely export, transfer and import today however.
- gcr 3y agonope, and that's (currently) by design! from a user perspective, passkeys are supposed to be impossible to duplicate. here are some workarounds: - you can log into your 1password on multiple devices - you can sign in by QR code, with the help of whichever phone has the passkey on it - you can add multiple per-device passkeys to your accounts of interest (for example, log into github on desktop and then add a passkey for your desktop device for that github) - you can keep all your passkeys on a hardware dongle - you can set up and keep all your passkeys inside an open-source manager (e.g. KeePassXC) For first-party systems, passkeys are supposed to be stored in hardware storage (TPM chips, secure enclave, etc). Once it's in the chip, the secret key's never coming out of those pins again (unless you're a nation state with a tunneling electron microscope and a very steady hand). (The huge exception is iCloud Keychain and whatever Google's doing for passkey sync, but that's importing from account data into hardware storage, not exporting existing credentials from a user's existing device)
- sholladay 3y agoYou are able to share an Apple passkey to any nearby Apple device at any time using AirDrop. Passkeys can also be used cross-platform during sign in via an NFC/Bluetooth handshake initiated by QR code. Additionally, passkeys are just a synced-via-cloud implementation of FIDO2, an open standard that has other implementations you may feel more comfortable using. For someone who requires being able to sign in to, say, GitHub from multiple different operating systems or platforms, you have a few options. 1. Use a passkey on your primary device, say an iPhone. You can still sign in to GitHub on a Windows computer or Android phone but you must have your iPhone with you. During sign in, there is an option to show a QR code on the Windows/Android, which you will point your iPhone at, and the two devices will do a secure handshake to sign you in. This is probably the worst option from a UX standpoint if you sign in on lots of devices that are not your primary. 2. Use a physical security key to store a FIDO2 key instead of a passkey. These devices are inherently cross-platform. Remember, a passkey is just a type of FIDO2 key. No one is forcing you to store it in the cloud. You can buy something like the YubiKey 5C NFC to store your keys completely offline and under your own control. The tradeoff is you will need to have it with you and you will need to plug it in every time you create an account or sign in. 3. Add multiple passkeys to your GitHub account, one for each platform you want to be able to sign in on. Unlike passwords, where an account generally only has one password at a time, it’s normal and even recommended to have at least one backup FIDO2/passkey registered with an account. And of course these aren’t mutually exclusive, you can mix and match these techniques, perhaps depending on how important the account is or how/where you typically access it. Maybe you only use a single passkey on your primary device for your bedtime social media scrolling, but use a passkey with a backup FIDO2 security key on GitHub.
- Wowfunhappy 3y agoBut what happens if I as an iPhone user want to switch to Android next year? Can I move my Apple passkeys?
- signal11 3y agoYou can use passkeys cross platform already, eg with 1Password or even KeePass XC. But I do agree with the point that Passkeys make it really easy to get locked in unless you’re careful.
- mikehollinger 3y agoI use 1Password to manage passkeys. It’s pretty nice. They sync across my devices, I can erase one if I need to, and generally with the exception of something odd with Firefox and one website they just work.
- dogman144 3y agoI think it’s about platform lock-in as well, tightly correlated to pivoting away from cookies due to regs and user pushback. If you read adtech docs, authenticated user sessions are the gold standard on enumerating user preferences for the sake of ads. Un/pw friction is noted as a difficulty in achieving this. Cookies developed the way they did in response, +/- details. If cookies go, then passkeys look a lot like a tangible and realistic solution to enumerating users via authn/z’d sessions, minus the friction of un/pw and a pw manager. IMO, the impacts of passkeys will feed right into this solution, and while I’m not sure if you can safely argue passkeys are a nefarious plan to replace cookie tracking, I don’t think you can get a tech giant to support such a reimagining of user experience if it didn’t have ancillary benefits beyond solely security use cases. When has a company like Apple or Google ever done such an equivalently large amount of work solely in support of security?
- umvi 3y agoYou can't trust Yubico?
- yawaramin 3y agoCreate a new passkey on the device? Or on the new device? I don't see why this is a big issue. Sure, it's slightly inconvenient to go through the 'create passkey' flow on a new device, but as long as the account you are using (let's say, GitHub) supports storing multiple passkeys per account and managing them online, there's no reason you can't.
- maeil 3y agoFor every single one of your 100+ accounts? What if you forget an account when doing so, then it's lost forever? If one of the 100+ websites is momentarily down I simply have to keep the old passkey provider around until it comes back up and then remember to switch just that one later?
- yawaramin 3y agoAre you using every single one of the 100+ accounts constantly? No? Then you can do the passkey flow on demand as needed. It can be comparably simple as an email login or 'we emailed you an OTP' login confirmation flow. If you never get around to using the account ever again in your life, I suppose you never needed it? If the website is momentarily down how are you going to access it with a password at that moment? You'd have to wait until it came back up. And then you could just as well set up the passkey.
- maeil 3y agoI'm referring to the process of switching where my passkeys are stored to a different place. E.g. moving from them being stored by Apple to them being stored by Google or any other provider.
- yawaramin 3y agoAnd I am talking about device-bound passkeys, not portable passkeys which can move around from provider to provider.
- deleted 3y ago[deleted]
- teekert 3y agoBitwarden? Proton?
- runeks 3y agoWouldn't this be solved by just having multiple passkeys for each account? You create one on your iPhone and another "backup" key from a desktop PC running some open source software. If your iPhone breaks you can always use the other. Similar to a server configured to accept multiple different SSH keys.
- dcow 3y agoYou are supposed to use multiple passkeys or you can use a password manager to store and sync your passkeys cross platform. Your passkeys sync in iCloud they aren’t device bound, just platform bound. Passkey export import is being worked on.
- lazyeye 3y agoYou can normally create multiple passkeys across different devices for the same login.
- juunpp 3y agoWebauthn, FIDO, etc. is run by a consortium of corporations whose goal is to be your sole identity provider and own your digital life. Nobody should have been hyped about this crap from day one.
- ParetoOptimal 3y agoWhat alternatives exist?
- cmurf 3y agoWhat about solokeys.com? As I understand it the workflow would be: * get a new passkey * enroll the new passkey with all existing services * unenroll the old passkey with all existing services That is certainly onerous for the "can my mom do this?" test. Like, I'm not even sure I want to deal with this myself and I have a Solo key (in a box). Further, seems any service I'd want to protect with a passkey, is also a service that would be very difficult to lose access to, should I lose the passkey (or it fails). Therefore I need to enroll two passkeys with each service, to have one as a backup. Uhh, OK. So now if I were to change passkey vendors/services - it's enroll two replacements, unenroll two? I haven't ever done this so maybe it's not as onerous as it sounds?