News for hackers. Stuff that matters.
Re:Issue 914451: Autofill does not respect autocomplete="off" by tus88 on Sunday October 13, 2019 @02:03AM (#21238639)
I would love it if someone explained how 'autocomplete=off' can lead to abuse of some kind. It seems to reduce the potential for security leaks.
Re:Issue 914451: Autofill does not respect autocomplete="off" by pilif on Sunday October 13, 2019 @02:18AM (#21238699)
It causes spec-compliant password managers to not work.

Unfortunately, disabling autocomplete for password fields is an often used form of security-theatre

Re:Issue 914451: Autofill does not respect autocomplete="off" by techsupporter on Sunday October 13, 2019 @02:42AM (#21238784)
Combine that with sites attempting to block pasting in a "complex, secure" password and I start to see Google's point here, bad as I don't want to. How "auth" is handled, at almost every layer, seems about as badly broken as "security" in the U.S. banking system.

Fortunately, Firefox gives me dom.event.clipboardevents.enabled so I at least need not worry about my workaround being broken.

Re:Issue 914451: Autofill does not respect autocomplete="off" by tmd83 on Sunday October 13, 2019 @05:35AM (#21239451)
Here's the tricky thing and I don't have a solution that doesn't get abused. I hate that lots of bank do this but I also have a use case for password autocomplete=off. We operate in an industry where shared computer access is very common and the risk of users saving password in browser is real and too high.

As I said don't know what the answer is. I definitely want someone using password manager be able to use them. Using a password manager is a conscious choice with setups involved. Browser's default autocomplete is often not. I don't know how to separate these two out.

Re:Issue 914451: Autofill does not respect autocomplete="off" by al2o3cr on Sunday October 13, 2019 @11:35AM (#21240934)
You could, I dunno, use the tools specifically provided to disable saving passwords in environments where that's undesirable:

https://thycotic.com/company/blog/2013/09/09/securing-web-br...

Re:Issue 914451: Autofill does not respect autocomplete="off" by epochwolf on Sunday October 13, 2019 @09:23AM (#21240219)
Isn’t it on the people administering those systems to disable autofill on their side?
Re:Issue 914451: Autofill does not respect autocomplete="off" by tmd83 on Monday October 14, 2019 @01:43AM (#21245538)
In theory it is. But for most customers (who are small) there's almost no IT department and the average computer literacy is lower than you might think (though improving) so the risk is there. Except for that situation I would happily leave them autofill/save password.
Re:Issue 914451: Autofill does not respect autocomplete="off" by pas on Sunday October 13, 2019 @02:23PM (#21241905)
kiosk mode? Firefox has a great extension for this.
Re:Issue 914451: Autofill does not respect autocomplete="off" by tus88 on Sunday October 13, 2019 @02:48AM (#21238808)
Ok, but how is that abuse? And if autocomplete=off is part of the html standard, how are the password managers spec compliant if they can't deal with it? Are people doing this just to annoy users who prefer password managers?
Re:Issue 914451: Autofill does not respect autocomplete="off" by Thorrez on Sunday October 13, 2019 @03:01AM (#21238865)
>Are people doing this just to annoy users who prefer password managers?

People are doing it because they don't understand password managers, and think blocking them makes people more secure. They believe that if a password is in a manager, that password is less secure than if that password was purely in the user's head.

Re:Issue 914451: Autofill does not respect autocomplete="off" by londons_explore on Sunday October 13, 2019 @04:05AM (#21239141)
If a bug in the password manager leaked the password to your bank to a third party, many users wouldn't want to pay for any associated costs/expenses when a bad guy steals their money.

Yet the bank also doesn't want to take on security audits for code entirely outside their control.

Re:Issue 914451: Autofill does not respect autocomplete="off" by Thorrez on Sunday October 13, 2019 @07:31PM (#21244032)
I consider that similar to a bug in the browser or the operating system. Should the bank require that I only use specific browsers or operating systems? In fact any program I install on my computer could have a vulnerability, or be malicious and thus lead to my password being stolen. Should the bank require that I not install any programs except ones they specifically permit?

The bank should also consider which is more frequent: user account compromises due to weak/reused passwords, or user account compromises due to password manager bugs.

Re:Issue 914451: Autofill does not respect autocomplete="off" by pas on Sunday October 13, 2019 @02:37PM (#21241993)
Then banks should recommend a good password manager. It's on them to make their users happy after all.

One part of that is a proper risk analysis. Password reuse and weak passwords are much bigger risks than a rouge autocompleter.

Re:Issue 914451: Autofill does not respect autocomplete="off" by rndgermandude on Sunday October 13, 2019 @06:18AM (#21239595)
Then only ignore autocomplete=off for forms that have password fields.

Sure, stupid devs can still work around that too, but so can they work around the current ingore-always behavior.

Re:Issue 914451: Autofill does not respect autocomplete="off" by flaviu1 on Sunday October 13, 2019 @02:17AM (#21238694)
> It seems to reduce the potential for security leaks

Misguided views like this are exactly how. Turning off autocomplete doesn't improve any sort of security, since the site already needs to trust the browser.

It serves no purpose other than to frustrate the user, and might even reduce security if it prevents the user from easily making use of a password manager.

Re:Issue 914451: Autofill does not respect autocomplete="off" by mike_pol on Sunday October 13, 2019 @02:25AM (#21238722)
Agreed on password fields, however if you have a webapp crm it causes so many problems. And also giving a solution of "hey just put something that we don't understand in the autocomplete so we won't try to autocomplete it" is really not a solution at all.

Imagine if instead of autocomplete it was something like ignoring font sizes/color because they detected that engagement was low when font size was whatever so they render it differently. A browser should render HTML not make decisions like these

Re:Issue 914451: Autofill does not respect autocomplete="off" by millstone on Sunday October 13, 2019 @02:38AM (#21238765)
You just described reader mode!
Re:Issue 914451: Autofill does not respect autocomplete="off" by kalleboo on Sunday October 13, 2019 @03:55AM (#21239100)
Reader mode is user-initiated though.

These developers wouldn't be complaining if the Autofill functionality was activated by a toolbar button rather than automatically.

Re:Issue 914451: Autofill does not respect autocomplete="off" by vidarh on Sunday October 13, 2019 @07:16AM (#21239784)
It does sometimes improve security for the user.

This happens when the auto-complete triggers on things it shouldn't and the user doesn't notice and submits personal details they never wanted to send to the site at all.

I've had to struggle a lot with working around Google's wrong-headed approach to this because this actually happens to real users. It's downright irresponsible, and I think frankly it's just a question of time before EU data protection watchdogs starts to take notice. All it will take is a sufficiently bad case of unintended disclosure of personal information (e.g. imagine a domestic abuse victim accidentally having their new address auto-completed in just the wrong situation).

(EDIT: this also easily happens with web apps where someone has to enter details for different users in the same forms multiple times; it get's very easy to end up not noticing Chrome auto-completing details for unrelated users; if that information is later visible to the user, it creates a real risk of leaking personal information)

Re:Issue 914451: Autofill does not respect autocomplete="off" by pyrale on Sunday October 13, 2019 @04:06AM (#21239146)
When user experience is bad, the website suffers, not chrome.

When chrome devs believe it is their role to alter ux, they are backseat driving.

Re:Issue 914451: Autofill does not respect autocomplete="off" by throwaway2048 on Sunday October 13, 2019 @02:22AM (#21238711)
plenty of stuff (like credit card info for instance) should absolutely never be auto-completed. The browser storing that sorta stuff to disk is stupid and completely avoidable.

Already caught chrome doing this to my Social Security Number before i disabled the functionality entirely. The idea of Chrome automatically auto filling any form it sees labeled "SSN" on any site dosen't inspire confidence.

Re:Issue 914451: Autofill does not respect autocomplete="off" by Thorrez on Sunday October 13, 2019 @03:06AM (#21238882)
> (like credit card info for instance) should absolutely never be auto-completed

One of LastPass's advertised features is credit card autofill. I assume they advertise it because some users like it.

https://www.lastpass.com/autofill

Re:Issue 914451: Autofill does not respect autocomplete="off" by xmodem on Sunday October 13, 2019 @02:35AM (#21238752)
One CRM webapp I worked on took our frontenders several attempts at different hacks to get Chrome to stop treating the SSN-equiv field as a credit card autofill.
Re:Issue 914451: Autofill does not respect autocomplete="off" by DCoder on Sunday October 13, 2019 @05:34AM (#21239442)
What are the odds that those hacks have been broken by Chrome updates since then?
Re:Issue 914451: Autofill does not respect autocomplete="off" by xmodem on Wednesday October 16, 2019 @11:10PM (#21278595)
Probably pretty high. I'm not on that team anymore, but the end users would have complained if it had happened.
Re:Issue 914451: Autofill does not respect autocomplete="off" by avodonosov on Sunday October 13, 2019 @02:54AM (#21238837)
From previous discussions I remember payment and bank forms use autocomplete=off and chrome developers don't like it, they want card numbers to be pre-filled.
Re:Issue 914451: Autofill does not respect autocomplete="off" by bonestamp2 on Sunday October 13, 2019 @03:41AM (#21239038)
I think some people want to be able to override it because some sites try to block password managers from filling the password field. Since Chrome has a built in password manager, that is likely their motivation to ignore it.