Re: Proposal:

>> We don’t want to cache or save specific locations since they may get stale, stateful things tend to become tracking vectors, and an HTML element sounds like a phishing injection vector.

Thinking about this more -- I'm not sure why this merits a well-known location. Everything else that the password manager knows about the login interface, it gets from the login page, correct? If so, it seems like putting this information there doesn't introduce any new security issues (since an XSS, etc. there is going to compromise the account anyway). 

Tracking doesn't seem like a relevant concern -- as long as the user has an account at the site, that's a far easier way to track the users' activity.

Again, not against using a well-known location on principle here, just curious as to why a new mechanism is needed here.


Mark Nottingham

Received on Wednesday, 4 April 2018 23:40:18 UTC