This article appears to be 100% AI. I guess there's some irony that a company ships an AI feature and someone else uses AI to come up with criticisms of that feature. But the article... doesn't actually say anything?<p>It's just full of weird, generic short-sentence LLMisms ("Detection is observation.", "Changing the password is authority.", "The security benefit is real.", "That is a meaningful improvement.", "This is not just text generation. It is an agent taking action with a sensitive credential.", ...). It doesn't offer any insights into the actual architecture that Apple came up with, whatever it might be. It doesn't propose a better design, other than a bunch of super-generic things that apply to <i>every single software project ever</i> ("The system should verify the exact website and account before filling or changing anything.", "This feature deserves focused adversarial testing during the beta period."). So... it's upvoted just because the title mentions Apple and AI?
Back in 1984, I wrote the original "obvious password detector".[1]
It just checks whether a password has English language trigram stats. This prevents dictionary attacks.<p>Everything is so much more complicated now.<p>[1] <a href="https://www.animats.com/source/obvious/obvious.c" rel="nofollow">https://www.animats.com/source/obvious/obvious.c</a>
There's this standard that is being worked on by the people working on the Passwords app at Apple (They are active on Mastodon, and often talking about that) which will probably be helpful for this feature too: <a href="https://www.w3.org/TR/change-password-url/" rel="nofollow">https://www.w3.org/TR/change-password-url/</a>
Thank you for this resource. I'm reading up on this spec and it seems like an interesting direction.<p>For anybody else trying to know what else the .well-known URI can hold: <a href="https://en.wikipedia.org/wiki/Well-known_URI#List_of_well-known_URIs" rel="nofollow">https://en.wikipedia.org/wiki/Well-known_URI#List_of_well-kn...</a>
I know that an uncommon name needed to be chosen, but something about the hyphenated /.well-known/ just turns me off.<p>I'd have really preferred another term: registered, reserved, defined, meta -- or really anything else.
got any of them mastodon links?
Call me when it can _delete the account_ from all those websites, which is likely the primary reason the user has not updated the password yet.
I’ve had the iOS password app <i>think</i> that it changed my password, when it did not, and then lose my old password.
Very curious if they're implementing browser driving themselves or using an off-the-shelf library like stagehand, browser-use, etc. to drive the DOM. Hopefully they open source it if it's in Swift.<p>A11y-tree alone is not enough for many sites because lots of auth stuff happens in OOPIF frames that need special handling/stitching/interactive element filtering.<p>There's also the issues of many captchas around auth stuff being implemented using canvas elements (that are hard to instrument for browser agents without relying on CUA). Can their on-device 3B model really handle accurate CUA driving? I guess we'll see...
I wonder whether the AI generated password that you allow to be created on your iPhone in the Passwords app can be recovered and added to whatever password manager you might be using on Windows or Linux desktop.<p>It seems like this is a great way to lock oneself out of access to an account on some of the devices that they own that do not have access to the Passwords data storage.<p>I can see where this can be a benefit in helping users secure their accounts with stronger passwords but I think that there is a lot of potential for this to become a real problem.
This could have nuclear level consequences. Imagine somehow your keychain is compromised. Using a change password URL means an attacker could literally lock you out of every account at the same time
this only really changes things for obscure sites. there's already automation readily available for all the popular social media, banks, crypto sites, etc.
[dead]
This is a great article except the "That can happen for plenty of boring reasons" list. Almost each of those reasons is completely unrelated to AI and can happen even if you attempt the change 100% manually with or without a password manager.
Yea, I saw that during the WWDC keynote and physically cringed. As the article says, what could go wrong?
Yes, also immediately thought of all the endless ways this could go wrong and end with someone losing access to their account, which depending on their account could be trivial or life altering, especially if their loss ends up being someone else's gain. Apple takes baby steps so I'm sure this will be limited in nature and most likely will get delayed until fully tested, but I'd definitely avoid testing during betas (with any real accounts that is).
People already have a hard time remembering passwords without them being automatically changed.
You <i>should not</i> be trying to remember your passwords. That's what autofill is for, so you can use passwords that are actually secure.
I can remember two passwords: the one that gets me into my laptop, and the one that gets me into my password manager. And this feature requires one to use Apple's default password manager, ergo...<p>And I shouldn't remember the first one, I just haven't gotten 'round to setting up the Yubikey on the laptop just yet.
That's the point of the password manager. You <i>shouldn't</i> be remembering individual passwords, they should largely be random.
If you're trying to remember passwords, you're already doing it wrong
people should not really be remembering any password other than the master password for their password manager.<p>this also <i>requires</i> the passwords app to even function. so this should be a non-issue.
Can it be turned off ?
As per the demo, in order for Siri to rotate your passwords "for you", you have to open the Password app, go to their dashboard on weak or exposed passwords, and click a button asking it to rotate your password account by account.<p>So yes. It's off by default. You have to affirmatively use the feature. (This is purely based on what I remember from the demo, mind you. I have not used the feature.)
This one is getting a lot of undue flak. Not only does it require explicit confirmation, it’s also contained entirely within the passwords app which already has access to all your passwords because you chose to trust it.<p>If you use this app, open it and look at how many entries fall under the “security” section. Everyday another password is compromised and added to the list, just too many to keep up. So, albeit apprehensively, I for one appreciate this feature.
I already let 1Password generate all my passwords, so as long as they're just invoking tools with AI rather than having it attempt manually, it doesn't seem like such a big deal?
<a href="https://xkcd.com/2044/" rel="nofollow">https://xkcd.com/2044/</a>
I mean isn't it either to complex to implement or not a good implementation kind off thing?<p>A good chunk of people do use devices other than apple eco system one's and if they try to login and then suddenly, you can't!
If they already use devices outside the Apple ecosystem, they're not using the Passwords app, or they're using the plugins that get you access to it in other ecosystems.
Isn't that a completely defeating attitude? V1.0 is rarely anything close to perfect.