15 ms·
A well-known URL for changing passwords
- deleted 8y ago[deleted]
- ancorevard 8y agoUsed by Safari for website password it identifies as used on multiple websites.
- isostatic 8y agoThey say that iCloud Keychain on iOS 12 and Safari 12 have implemented this feature. And sure enough, https://www.icloud.com/.well-known/change-password https://www.icloud.com/.well-known/change-password Looking through the referenced RFC, there's a whole raft of "well known" urls that are registered https://www.iana.org/assignments/well-known-uris/well-known-uris.xml https://www.iana.org/assignments/well-known-uris/well-known-... How widely adopted are these?
- codeulike 8y agothey are not well known
- Someone1234 8y agoThe one that Apple's browsers request on every domain isn't even in the list: /.well-known/apple-app-site-association That's the only .well-known request we have in our logs from the last year or more. Seems to be looking for an app associated with our site. Aside from that, I don't know anyone or anything else using .well-known. Seems to be an Apple thing.
- eponeponepon 8y agoI think LetsEncrypt uses it, no?
- webignition 8y agoYes, /.well-known/acme-challenge is used by LetsEncrypt.
- toupeira 8y agoYes, also OpenID Connect.
- merb 8y agosadly only for discovery. but it would be great if oauth/openid connect would actually use .well-known/authorize, etc. instead each provider has it's own sauce.
- JeremyBanks 8y agoYes, also Keybase.
- xena 8y agoFound documentation on it for you: https://developer.apple.com/library/archive/documentation/General/Conceptual/AppSearch/UniversalLinks.html https://developer.apple.com/library/archive/documentation/Ge...
- Someone1234 8y agoThe discussion was about specs/standards for .Well-Known. I pointed out that Apple's isn't in the list. In that context I don't follow why you think linking to Apple's development guide helps clarify anything? It still isn't a specified standard, and still isn't on the list of them.
- geofft 8y agoYou stated you were unsure what it was. The link clarifies that. And it is a specified standard: the link is the specification. It's not a standard developed by a multi-stakeholder standards organization, but there are other kinds of standards, too.
- saagarjha 8y agoIt really has no utility outside of Apple's app ecosystem, so why would you want it to become a standard?
- WorldMaker 8y agoWebFinger, a key underlying tech of the Fediverse and used for bootstrapping OpenID Connect, ActivityPub, and many other standards uses .well-known. https://webfinger.net/ https://webfinger.net/
- ushi 8y agoThunderbird looks for http://domain.tld/.well-known/autoconfig/mail/config-v1.1.xml http://domain.tld/.well-known/autoconfig/mail/config-v1.1.xm... for autoconfiguration. See: https://developer.mozilla.org/en-US/docs/Mozilla/Thunderbird/Autoconfiguration#Configuration_server_at_ISP https://developer.mozilla.org/en-US/docs/Mozilla/Thunderbird...
- dandr01d 8y agoYes
- tzs 8y agoGnuPG can use /.well-known/openpgpkey since 2.1.12, and it is used by default since 2.1.23, when you do --lookup-key. E.g., $ gpg --lookup-key foo@example.org will include among the places searched /.well-known/openpgpkey/hu/<some-sort-of-hash-looking-thing>?l=foo at example.org It also looks at /.well-known/openpgpkey/policy. Toss in "-auto-key-locate=clear,wkd,nodefault" to force it to look there for the key even if it already has a key for that email address.
- Leace 8y ago<some-sort-of-hash-looking-thing> is ZBase32(SHA1(localPart)) and the standard is described here: https://wiki.gnupg.org/WKD https://wiki.gnupg.org/WKD If one controls a domain, has HTTPS set up and uses PGP this is the easiest and most secure way to host a key (`gpg --list-keys --with-wkd $KEY` shows the hash value). Enigmail, Mailpile, Mailvelope will automatically discover the key when composing an e-mail. ProtonMail is also working on integration of WKD with their web mail.
- jtl999 8y agoAs a site owner, how many of those should you handle? Already do special handling of acme-challenge for Let's Encrypt/ACME but that's a given.
- tialaramex 8y agoAs a site owner the main thing you should do about .well-known is be aware that it's special and so e.g. if you add a feature where users get a vanity page at www.example.com/username you shouldn't let them have the username .well-known The leading dot is there both because that is already special in POSIX and because there's a good chance your validation whitelisting already forbids leading dots, just like newlines, slashes and other characters we can expect to cause mayhem. So this was a less dangerous choice than just well-known without the dot.
- mikeleung 8y agolooks like the change was proposed by an apple WebKit developer: https://github.com/hober https://github.com/hober which would explain why apple has implemented it...
- hober 8y agoYup, hi.
- intern4tional 8y agoRegardless of what happens, thank you for trying to make the web a better place.
- devman0 8y agoApparently https://github.com/.well-known/change-password https://github.com/.well-known/change-password also works.
- wolfgang42 8y agoActual spec here: https://wicg.github.io/change-password-url/index.html https://wicg.github.io/change-password-url/index.html
- gregmac 8y agoThis is a nice simple convenience feature, for sure [1]: > example.com provides a /.well-known/change-password resource which redirects to their change password form, wherever it happens to already be. > Password managers check for the existence of /.well-known/change-password on https://example.com https://example.com. > If it's there (the response code is 2xx or 3xx), the password manager can cause the user's browser to navigate there when the user indicates they'd like to change their password. It's not trying to enforce a particular password schema, it's not an API endpoint to automate changing passwords, and it is not trying to dictate site design or form layout. It's also dirt simple to implement with practically zero cost. Aside from Safari, it doesn't seem like any password managers have implemented this yet. It's also not in the IANA well-known URI registry [2] yet (even as draft), so that would probably at least allow it to get a bit more traction. Apparently they are working towards that [3]. [1] https://github.com/WICG/change-password-url/blob/gh-pages/explainer.md#proposal https://github.com/WICG/change-password-url/blob/gh-pages/ex... [2] https://www.iana.org/assignments/well-known-uris/well-known-uris.xhtml https://www.iana.org/assignments/well-known-uris/well-known-... [3] https://twitter.com/rmondello/status/1042008520105779206 https://twitter.com/rmondello/status/1042008520105779206
- Immortalin 8y agoHere's an open source version of the common password rotation feature in most online password manager services: https://github.com/ddevault/pass-rotate https://github.com/ddevault/pass-rotate
- tomjakubowski 8y agooff topic but I'm dying to know: why is the "American Society of Heating, Refrigeration, and Air-conditioning Engineers (ASHRAE)" in the "People" section of that IANA well-known URI list?
- schoen 8y agoIt's apparently because of an HTTP-based home automation protocol: http://www.bacnet.org/ http://www.bacnet.org/ http://www.bacnet.org/Addenda/Add-135-2012am-ppr3-draft-17_chair_approved.pdf http://www.bacnet.org/Addenda/Add-135-2012am-ppr3-draft-17_c...
- hannob 8y agoThat looks like a good idea, but why not go one step further? Provide a common API interface for password changes. Think about it: If you assume your pw manager database is compromised - what do you do? Go to a hundred webpages and change your password? probably not. Your PW Manager can't provide a feature to do it for you. But it could if there was such an API.
- dmurray 8y agoDashlane has that feature [0], though not for all sites of course. I haven't tried it out but I don't see why they couldn't have it working for say the 1000 most popular sites, which would cover at least half of my needs. [0]https://support.dashlane.com/hc/en-us/articles/202699281-How-to-use-Password-Changer#title3 https://support.dashlane.com/hc/en-us/articles/202699281-How...
- toyg 8y agoLastPass had a similar feature when I used it. It often broke and was overall unreliable, as all scrapers are wont to be. Worse - when it failed, you couldn't be sure at what point of the process it had done so, leaving your accounts potentially inaccessible.
- dmurray 8y agoThat's a good point. I guess they should keep the new and the old password until you've successfully logged in with the new one.
- asdkhadsj 8y agoOn that note though, if we start using standard APIs for this sort of thing, I question whether we should just go farther and "solve" the problem. Ie, as a dumb example, why should I expect them to implement an API for my password manager, and instead not simply allow oauth where my pass manager becomes my token provider? Doesn't that fake example solve both problems, while also getting rid of bizarre password churn? Sure, it has the downside of "what happens when my password provider is compromised.." but that's always true, right? An API for password managers feels like a solution to a problem we've created. Don't get me wrong, I love the idea of reducing password churn. I'm just not sold on this specific method of handling it.
- janzij 8y ago[removed]
- ntzm 8y agoAnd?
- Someone1234 8y agoSeems like a nice subtle way to hijack the changing password mechanism, particularly on a sub-domain you control. Just set the URL to e.g. "https://evilsite/changepasswords" https://evilsite/changepasswords" and wait for Password Managers to be updated. The fact that the spec says nothing about where a user can be redirected, and which domains/sub-domains are within scope for which change password requests seems like an oversight. For example if my password manager saves a password for login.example.com, is a .well-known/Change-Password on evil.example.com, or example.com in scope? Who decides? Is it left to the password manager to figure out the security scope?
- CGamesPlay 8y agoWell, since password managers already tie a password to a specific domain, presumably they would use the same logic for determining the scope of the well-known URL. I do agree that the spec could probably benefit from clarifying this, but I bet "the same domain as one of the recorded login URLs" is sufficient. (And the password manager would never even know to check evil.example.com if you hadn't ever put that password into that subdomain).
- Someone1234 8y ago> but I bet "the same domain as one of the recorded login URLs" is sufficient. What is that a quote from? I cannot find it in the spec here: https://wicg.github.io/change-password-url/index.html https://wicg.github.io/change-password-url/index.html
- CGamesPlay 8y agoSorry, intended as a hypothetical suggestion, not a quote.
- Someone1234 8y agoOh understood. Yeah that suggestion would fix my concerns almost wholesale. They just need to think about scoping it to e.g. domain, subdomain, etc.
- deleted 8y ago[deleted]
- JackC 8y agoI see the argument for simplicity, but I think it would be much more impactful to have a well-known URL for automated password changes. It's common to see advice to "change all your passwords" following incidents like Heartbleed or Cloudbleed or after having a personal computer hacked.[0] This advice is useless -- it's way too time consuming, and also comes too late. If you need to change all your passwords now, you actually needed to do it six months ago. A well-known URL that specified password requirements and an endpoint to hit with username, old and new passwords would let password managers reliably and routinely update passwords instead. To the extent "change all your passwords" is ever good advice, it would become advice you could follow automatically instead of never. [0] Example of the form: https://securitywatch.pcmag.com/hacking/322494-heartbleed-fallout-change-all-your-passwords https://securitywatch.pcmag.com/hacking/322494-heartbleed-fa...
- Klathmon 8y agoThere's room for both ideas. This one has the benefit of being stupid simple to implement and maintain. In 10 minutes I can throw this together for all of our login stuff. But a fully automated password changing system/API? That's not exactly as "maintenance free". Now you are maintaining a full API separate from your normal routines, and it's in an area that I always advocate for simplicity since subtle mistakes can mean compromised accounts. And the "fully automated" API would also have to work with "multi-factor" systems, which alone make everything more complicated to cover all the different ways it's done. Don't let the possibility of a better solution kill the benefits of this simpler one.
- peterwwillis 8y agoHere is the actual spec: https://wicg.github.io/change-password-url/index.html https://wicg.github.io/change-password-url/index.html Presumably this is only for accounts you are already logged into and want to change the password of, since change password forms usually aren't accessible unless you are already logged in. However, the same domain may involve multiple account types. AWS and other popular websites have multiple types of accounts, different login methods, and different change-password forms, on the same domain. If all this URL does is redirect to one single page per domain, it won't work for cases of more than one type of login. Also, it seems that password reset is a lot more common than just changing a password, so maybe this spec could be extended to that form, too?
- therealtbs 8y agoUsually the place where you realize you forgot your password is the login form. So the 'standard' link/button/whatever below/next to/in proximity of the login form works quite well for this. Since the spec is intended for password managers and other user agents, it makes sense to have a standard location to access such functionality. Also the page could be anything (i.e. doesn't have to be a redirect) so theoretically AWS could set up an account chooser that has links to all the appropriate places for your accounts
- WorldMaker 8y agoWhere it links would be up to the website. The password manager doesn't know if you are already logged in or not, just that the user requested an intent to change their password at example.com. The password manager should just open the URL in the user's default browser. Then it's up to the website itself to redirect to a login flow if need be (they don't have a logged in cookie on that browser), including the password reset flow if necessary. If a website has more than one account type that the user might want to change the password for, it could add some sort of flow to ask which account was meant. If the user has more than one account at the website, that becomes up to the user to make sure they signed into the right one that they wanted to password change. If the website is aware the user may have more than one account (such as Google's account switcher), they could present the options directly then. It seems easy enough to do the right thing in most cases, given how simple this proposal is.
- Sir_Cmpwn 8y agoI was looking to do this for my pass-rotate project: https://github.com/ddevault/pass-rotate/issues/1 https://github.com/ddevault/pass-rotate/issues/1 I hope a spec gains traction.
- pbnjay 8y agoooh can we also get /.well-known/delete-account ?? seriously though, I would love this for all those sites that bury it as far as possible...
- NickBusey 8y agoThis would be great, but like you said, the sites you would really want to use this for would likely never implement it. Unless it were a requirement of something like GDPR..
- gwbas1c 8y agoThe real problem is that every single site needs its own separate password. (Even worse are products and services where you need a separate password for different features.) The better way to solve this is to push for better account portability. We already (kind-of) have this with websites that let you sign in with your Google or Facebook ID. (Unfortunately, these systems still have privacy problems because they share your email, or the web site fails if you don't want to share your email.)
- 0xfeba 8y agohttps://www.grc.com/sqrl/sqrl.htm https://www.grc.com/sqrl/sqrl.htm Though I think he will need a more convincing marketing site if he intends for people to try it out.
- Piskvorrr 8y agoGRC is not known for giving much importance to marketing.
- avaika 8y agoThat is not a problem at all. Whenever you have a centralized oauth service, there will be a possibility to track its user. I don't see a way how any company might guarantee that it doesn't track me so I'd believe it. Therefore I'd prefer to have an alternative to oauth with old school account creation on each and every website with separate login/password pair.
- opless 8y agoWe really should have public keys that we can give away to these sites, and then there should be a challenge/response phase that our private keys (stored safely!) are used to sign the challenge. Of course that would mean you carrying around a physical token that needed to talk to your browser(s), phone(s) etc. Passwords should GTFO tbh.
- Tharkun 8y agoThis nonsense comes up every time anything related to a password is mentioned. Google & Facebook login are evil. And people end up picking stupid Google & Facebook passwords anyway. Every single site needing its own password is a feature, not a bug. Educate people about password managers instead.
- janikvonrotz 8y agoIt up to browser standards to make this thing reality. example.com does not have any incentive to provide this url. However, if a users browser would treat sites implementing this feature as "more secure", example.com will gladly implement it.
- noResetPage 8y agohttps://wicg.io/.well-known/change-password https://wicg.io/.well-known/change-password Also: https://news.ycombinator.com/.well-known/change-password https://news.ycombinator.com/.well-known/change-password
- ghostly_s 8y agoFrom the spec: > Servers must not locate the actual change password page at the change password url, per RFC5785 §1.1 Appropriate Use of Well-Known URIs. I scanned the RFC but can't fine the prohibition against this. Curious, why does it matter? Just because .well-known URLs are not meant to be exposed to the user?
- TazeTSchnitzel 8y agoThat section says: There are a number of possible ways that applications could use Well- known URIs. However, in keeping with the Architecture of the World- Wide Web [W3C.REC-webarch-20041215], well-known URIs are not intended for general information retrieval or establishment of large URI namespaces on the Web. Rather, they are designed to facilitate discovery of information on a site when it isn't practical to use other mechanisms; for example, when discovering policy that needs to be evaluated before a resource is accessed, or when using multiple round-trips is judged detrimental to performance. I am guessing they consider “general information retrieval” and “URI namespaces” to exclude it.
- ghostly_s 8y agoI did see that section, but don't see how it follows. Putting your PW reset page at this address would be using the URI spec for exactly it's intent, not “general information retrieval”. My read of this clause is just that they don't want you to start using .well-known as your primary namespace or cluttering the registrations with junk that's not broadly applicable.
- hober 8y agoThis is being tracked by https://github.com/WICG/change-password-url/issues/9 https://github.com/WICG/change-password-url/issues/9
- michaelmcmillan 8y agoAllow me to change username/email while I'm at it!
- tnorthcutt 8y agoAfter learning about this a few days ago, I created a Laravel package for managing .well-known URLs: https://github.com/tnorthcutt/laravel-well-known https://github.com/tnorthcutt/laravel-well-known I plan to add other URLs that make sense as well.
- juancampa 8y agoI haven't read the proposal but it made me think of something like: /.well-known/personal-access-token To get an access token for API access to my own data. You know, for our right to be represented by a bot[1] [1] https://continuations.com/post/172413445510/we-need-mandatory-enduser-apis-for-social-and https://continuations.com/post/172413445510/we-need-mandator...
- crescentfresh 8y agoCan someone clarify, is this actually for resetting a forgotten password? I don't quite follow. example.com's change password functionality should be behind an authenticated page that requires a) the user be already logged in, and 2) the user's current password (for confirmation). Whereas example.com's forgot/reset password functionality is usually a wide-open page anyone can reach to begin the process of password reset (more inline with what this spec seems to be describing).
- intertextuality 8y agoDid you read the explainer? > Currently, if the user of a password manager would like to change their password on example.com, basically all the password manager can do is load example.com in a browser tab and hope the user can figure out how to update their password themselves. > The goal of this spec is to do the simplest possible thing to improve this situation. It's an attempt to standardize the endpoint for changing a password. Which is kinda random for each website currently.
- crescentfresh 8y ago> Did you read the explainer? I did. My confusion arose from it. Something is clear to you that is not to me :)
- JW_00000 8y agohttps://news.ycombinator.com/.well-known/change-password https://news.ycombinator.com/.well-known/change-password will just redirect to https://news.ycombinator.com/changepw https://news.ycombinator.com/changepw. If the user isn't logged in, that page asks the user to log in.
- crescentfresh 8y agoAh I see, and from the perspective of a password manager it would know what password to fill into the password field to get the user into the site. After that, once on the change password screen said manager would also take over generating a new password, yes?
- polemic 8y agoTo be pedantic, 'well known' things are not usually specified in advance :D
- curo 8y agoThis is so relevant. Just 10 mins ago, I got a short, casual, no-reply email from Teachable about an email & passwords breach. If you're a startup and you're storing plaintext passwords out of expediency, realize you're doing a massive disservice to your customers. It seems they changed this in 2015, but didn't go back and fix it for their earliest adopters. Your early adopters make you what you are! Protect their data. And if you do mess up, don't send out a self-focused apology from a no-reply address. We are writing to inform you of a suspected data breach involving accounts created between September 17, 2013 and November 21, 2015. We have reason to suspect that personal information related to accounts on Bitfountain (joined 2014-08-18) may have been compromised. This includes the email addresses and passwords associated with the school's Teachable (formerly Fedora) account. As a precaution we are enforcing password resets...If you happen to use this password with any other service, we highly recommend updating your password there as well. We apologize for the inconvenience, and thank you for your understanding in helping us keep Teachable safe.
- pc86 8y agoStoring plaintext passwords is no faster than storing a cryptographically secure hash of the same password. We're not even talking lines of extra code, just a few extra characters actually hash the input. It's not expediency, it's laziness bordering on criminal stupidity/negligence.
- hamandcheese 8y agoOr maybe just ignorance?
- pc86 8y agoProtecting a user's password is such a basic level of understanding I think ignorance falls under "criminal stupidity" for this one.
- dragonwriter 8y agoIgnorance of facts that any reasonable exploration of best practices in the area you are working in would reveal, in a commercial venture, is a product of laziness (or hubris) bordering on (or crossing into) negligence.
- nly 8y agoI'd rather we hade /.well-known/delete-account
- IloveHN84 8y agoBut works only on Apple devices..so in a very small amount of devices
- greycol 8y agoA lot of people in this thread seem to be unaware of the purpose of /.well-known/ . You can read the memo about it here: https://tools.ietf.org/html/rfc5785 https://tools.ietf.org/html/rfc5785 Basically /.well-known/ is a place to check for common site meta data and you can suggest new urls that can be registered. /.well-known/change-password Has been accepted and added for the use case of pointing to where to change your password. If you think this is insufficient then there is nothing stopping you from trying to put forward a more comprehensive proposal for say /.well-known/change-password-api that would contain all the meta data for whatever standardized scheme for informing multifactor/username/email api combinations you eventually come up with. Just because /.well-known/change-password exists it does not in any way limit what other suggestions can be made and implimented later (it only means that you need to use a different url).
- amelius 8y agoDon't we have AI by now that can figure out what button to click to change the password?
- soheil 8y ago> If it's there (the response code is 2xx or 3xx), the password manager can cause the user's browser to navigate there when the user indicates they'd like to change their password. The primary issue I see here is that there are a lot of websites that do 301 redirects from either non-www to www subdomain or non-https to https, would this not confuse the password managers in assuming there is a .well-known even though it’s just a benign redirect?
- hober 8y agoThis is being tracked by https://github.com/WICG/change-password-url/issues/4 https://github.com/WICG/change-password-url/issues/4
- edanweis 8y agoHow about a well-known URL for unsubscribe?
- IAmLiterallyAB 8y agoNot quite the same thing, but there are official email headers for unsubscribing from email mailing lists. https://tools.ietf.org/html/rfc2369 https://tools.ietf.org/html/rfc2369
- soheil 8y agoOne thing I really wish when it comes to Firefox Containers if I create a container for Gmail and am logged into Google I want all the email links (mailto:) to open in that container. I know currently you can have all the sites with a specific URL to open in specific containers but I'm not sure if there is a way to open various protocols in separate containers.
- andrethegiant 8y agoNote to self, create some express middleware that listens to .well-known GETs and redirects to a map of developer-supplied URLs.
- choward 8y agoYou really only have one password for web sites with password resets via email and that's the password to log into your email account.
- ndnxhs 8y agoYES, this is what I have been waiting for. A month ago I lost a USB with my keepass file on it. The file is encrypted with a good password but I would feel better if I could reset all my passwords just in case but that would take me days.
- masa331 8y agoI wish every site would just use emailed sign-in links instead of passwords. We wouldn't have to deal with all these password relative nonsenses - password managers, .well-knowns, password requirements, password resets, weak passwords, gazilion passwords in my head. Everything would be so much simpler
- epse 8y agoAnd then your email gets compromised and everything is immediately lost? No thanks