News for hackers. Stuff that matters.
Re:Issue 914451: Autofill does not respect autocomplete="off" by jchw on Sunday October 13, 2019 @03:10AM (#21238907)
Because other people here are throwing in their frustrations, I will at least add that on the flip side I have been frustrated by sites that attempt to disable autofill for illegitimate reasons, like attempting to disallow password managers. I think I understand where this is coming from.

On the other hand, I, too, have been bit by this at least once, in the past. I think it was easier to just disable it at that time, but IIRC, the solution we landed on was to not use form controls at all but switch said text controls over to use content-editable elements. In our case it made sense, since it was not a form at all. My memory could be a bit hazy here, though.

(I do not work on Chrome or use Chrome at home, but as disclosure I do currently work at Google.)

Re:Issue 914451: Autofill does not respect autocomplete="off" by gnud on Sunday October 13, 2019 @06:35AM (#21239645)
Chrome explains in their security FAQ [0] why they don't adhere to autocomplete=off for password fields.

They could still follow it for other fields.

0: https://chromium.googlesource.com/chromium/src/+/master/docs...

Re:Issue 914451: Autofill does not respect autocomplete="off" by kevincox on Sunday October 13, 2019 @08:09AM (#21239956)
Of course then websites will just stop using password fields and that is awful for security and convinced.
Re:Issue 914451: Autofill does not respect autocomplete="off" by kerng on Monday October 14, 2019 @03:02AM (#21245819)
Shouldn't the work on changing the spec, rather then confusing majority of developers and causing even financial loss and embarrassment for many? This thread is filled with cases where this caused issues.

Google should spend their cycles to work on a standard for password managers. The current design of those is flawed anyway.

Re:Issue 914451: Autofill does not respect autocomplete="off" by anoncake on Sunday October 13, 2019 @03:40AM (#21239031)
I think we need a way to disable features only for those developers that abuse them. Like uMatrix but built-in and with rules being supplied automatically as ad blocking lists are.

You autocomplete=off a password field? That attribute won't have an effect on your site anymore.

You auto-play videos when the user doesn't expect it? What videos? The web doesn't support videos – as far as you are concerned.

Scroll hijacking? I hope you used progressive enhancement because you just lost your Javascript privileges.

Re:Issue 914451: Autofill does not respect autocomplete="off" by Roritharr on Sunday October 13, 2019 @04:31AM (#21239236)
This is actually a reasonable proposal. A moderate list could be an in-built feature, with some config options.
Re:Issue 914451: Autofill does not respect autocomplete="off" by anoncake on Sunday October 13, 2019 @01:57PM (#21241742)
It would only work if a strict list is the default in browsers that developers are not willing not to support. The point is not to hack around user-hostile patterns. That frequently means entering an arms race you cannot win. Even in the best case, you're doing that site developers' job. Badly: You have to remove the bad stuff while avoiding overblocking. That's a lot harder than not adding it to start with.

I'm proposing to take away tools from developers that abuse them no matter how much that breaks. If you mine bitcoins or annoy the user using pop-ups we shouldn't spend time finding out what scripts are good and which are bad but just disable all of them, till you remove the user-hostile stuff. We just broke your SPA? That's your problem. Better start working then.

Re:Issue 914451: Autofill does not respect autocomplete="off" by basch on Sunday October 13, 2019 @11:50AM (#21241023)
I asked if something similar was coming to Brave, and the answer was yes. Opera maintained what i believe was a somewhat community powered site patching repository back in the Presto days.

https://news.ycombinator.com/item?id=20831774

Re:Issue 914451: Autofill does not respect autocomplete="off" by msclrhd on Sunday October 13, 2019 @05:35AM (#21239448)
Can we have a reliable cross-browser way to say "this is a change password field, so don't autocomplete it" and "this is an email address field not a username field, so don't autocomplete it with the login username"?
Re:Issue 914451: Autofill does not respect autocomplete="off" by shdon on Sunday October 13, 2019 @08:43AM (#21240073)
The autocomplete="new-password" (or autocomplete="off" or even autocomplete="some-random-nonsense") method is supposed to be doing that according to the spec. It is ignored by browser developers probably due to abuse. Additionally, all of those also trigger the prompt to save the password. For a password change form, that is the right thing to do, for many others it is not.

I'd very much like to see a way to disable that save prompt too, especially in user management screens. When I create a new user, I want neither my own password to be autofilled, nor do I want to overwrite my saved password with theirs.

Re:Issue 914451: Autofill does not respect autocomplete="off" by Santosh83 on Sunday October 13, 2019 @06:02AM (#21239535)
The web needs strong typing. Right now most input fields are variants of text boxes and there are no naming standards that can be enforced without breaking millions of sites.
Re:Issue 914451: Autofill does not respect autocomplete="off" by edoceo on Sunday October 13, 2019 @05:46AM (#21239484)
I've seen/used autocomplete="new-password"
Re:Issue 914451: Autofill does not respect autocomplete="off" by anoncake on Monday October 14, 2019 @06:54AM (#21246839)
Developers can say that. What we need is a reliable way to know if they're lying.
Re:Issue 914451: Autofill does not respect autocomplete="off" by anticensor on Sunday October 13, 2019 @05:37AM (#21239458)
I even found a name for such an extension: PunishIt.
Re:Issue 914451: Autofill does not respect autocomplete="off" by doctorpangloss on Sunday October 13, 2019 @03:23AM (#21238959)
Disabling autocomplete is so incredibly frustrating that I ran an extension in Safari to remove the off tag from sites. Of course I want to use KeyChain, the whole point is that touch based ID is more secure.
Re:Issue 914451: Autofill does not respect autocomplete="off" by Nitramp on Sunday October 13, 2019 @04:30AM (#21239235)
I have my own extension for Chrome that yanks the autocomplete attribute. I much rather deal with over eager completion than websites disabling it for silly reasons and pseudo security.
Re:Issue 914451: Autofill does not respect autocomplete="off" by httpsterio on Sunday October 13, 2019 @07:15AM (#21239781)
Touch based are not better. Your fingerprint is not a password, it's just an identifier and shouldn't be treated as a secret.
Re:Issue 914451: Autofill does not respect autocomplete="off" by geofft on Sunday October 13, 2019 @08:27AM (#21240022)
Your fingerprint is an additional factor (something you are) for the actual better-than-passwords thing here, the isolates processor/storage in your laptop that handles Touch ID (something you have). Without physical possession of the laptop, the fingerprint is useless.
Re:Issue 914451: Autofill does not respect autocomplete="off" by dustinmoris on Sunday October 13, 2019 @07:35AM (#21239852)
> Your fingerprint is not a password

Correct, because a fingerprint makes a password to some extent redundant.

> it's just an identifier and shouldn't be treated as a secret

Correct, identifiers are not secrets. Your face is not a secret and your fingerprint either. The problem is that we use secrets to identfy someone, when we potentially already have tech which can identify someone without having to remember a secret and store it in a dictionary of secrets on someone else's computer in the cloud.

The sole purpose of a password is to identify someone with a certain degree of confidence. If a fingerprint taken from a handheld device, which has already been proven to belong to a person, can provide the same if not even a higher level of certainty about someone's identy, then a password or as you say "secret" is not required at all anymore.

Re:Issue 914451: Autofill does not respect autocomplete="off" by NeedMoreTea on Sunday October 13, 2019 @07:55AM (#21239910)
Um no. The user Name or ID is to identify.

The password is to secure that identity. With TouchID or FaceID you are using them for both. Which reduces security.

> then a password or as you say "secret" is not required at all anymore

Definitely incorrect. Someone can cut your finger off, lift a print off your coffee mug, extract it from a selfie etc. There's been dozens of ways to exploit over the years, many of which have hit HN.

Re:Issue 914451: Autofill does not respect autocomplete="off" by dustinmoris on Sunday October 13, 2019 @11:59AM (#21241068)
What is the compromise? What is insecure about me being me? Either we talk past each other not understanding each other's point, or I feel like you profoundly misunderstand the reason for people using username/password for authentication nowadays?

With most things you need to authenticate to gain access. Authentication is only trying to solve one question - identifying that a person is who they say they are. If I walk home and my wife sees me, she can identify me immediately by simply seeing my face and other biological attributes which gives her 100% certainty that I am who I am, therefore she doesn't question me on entering the house or calls the police.

If I was to go through some top secret lab experiment which would change my look (make me younger by 10 years or something) then I'd struggle to walk home and convince my wife that I am me without providing additional evidence, like sharing some secrets which only she and I know and we know that nobody else would know.

With technology so far we didn't have the ability to identify someone as confidently and as fast via biometrics (like my wife does) as via other means, which is why a few decades ago we had to invent a workaround, namely username and password - which is a secret that hopefully only me and the website knows. This was to date the best way to identify someone, but times are changing fast, as as biometric identificaiton via technology is advancing fast, we are more and more removing the need of username + password for authentication.

Hope now my point makes sense.

Re:Issue 914451: Autofill does not respect autocomplete="off" by NeedMoreTea on Sunday October 13, 2019 @01:15PM (#21241483)
A biometric identifies you. An identity does not inherently authenticate you.

Identification is knowing which account to log in. dustinmoris, User123 or user124.

That alone is useless, as anyone who knows your name could log in. So we need to add security to authenticate you. To authenticate with reasonable certainty that the person accessing dustinmoris actually is Dustin Moris, at this moment willingly accessing their own account, willingly transferring £1m to NeedMoreTea. :)

Now, it's certainly true that biometrics are uniquely associated with you, but prove identity not authentication - bear with me here.

You leak DNA and fingerprints all over the place, constantly. Fingerprints have even been picked up from photos. That makes fingerprints surprisingly weak authentication. Face IDs have been fooled by video and photos. I'm not at all current on what the state of the art on FaceID hacking and devices is, so can't say more there. In a police interview they can place your thumb on the phone or wave phone under your face. Maybe borrow your thumb while you sleep to transfer that £1m. The bank will say you fully authenticated it, in their highly secure app, you will deny it.

In combining biometrics as identification and authentication we've compromised the system. It does not give certainty, or even especially high confidence. If motivated, anyone in your office could lift a print while you're out. Computer or phone says Dustin Moris is believed awake and accessing, but you're certainly not doing so willingly, nor can you resist if just a touch or look unlocks. In this context, your wife might easily pick up on whether you were willing in a police interview or not, the phone can't, because mere identification is the unlock.

With a password they have to persuade you to reveal it. It is very easy to not leak passwords accidentally on PostIts, and manage the complex with a password manager. The police can certainly beat it out of you, but most places are supposed to have rules against that. Many places actually honour those rules. A judge might question the bruises and missing teeth.

For a lot of people that's a fine distinction that doesn't matter, the convenience of it probably being you willingly unlocking the phone with your thumb is good enough. If security actually matters, it's not.

Sorry that got a bit long.

Re:Issue 914451: Autofill does not respect autocomplete="off" by kortilla on Sunday October 13, 2019 @02:37PM (#21241992)
You highlight flaws in faceid, etc but passwords also have flaws.

- Fingerprints can be lifted from pictures. - Passwords can be forgotten and thus have seriously flawed reset schemes that often fallback to something as simple as having the right phone or backup code. - passwords can be lifted by keyloggers - passwords can easily be phished - passwords can be shared

Authenticating access can come from 1 or more of: something you know, something you have, something you are.

They each have flaws. They all do the same thing.

Re:Issue 914451: Autofill does not respect autocomplete="off" by NeedMoreTea on Monday October 14, 2019 @02:53PM (#21251489)
They don't do the same thing. All the flaws in passwords can be avoided, the semi-public state of biometrics cannot.

Authenticating access, if you follow standard security practice, should be at least two of, and preferably all three of: something you know, something you have, something you are. Not one or more.

Re:Issue 914451: Autofill does not respect autocomplete="off" by kortilla on Monday October 14, 2019 @08:32PM (#21254402)
There is no axiom that the flaws of biometrics cannot be avoided. “Something you know” is in fact a biometric property of the brain that can easily be transferred.

Touch ID combines something you have with something you are. It’s easily better for 99.9% of the threats out there that result from weak passwords shares across sites and users trained to type them into anything that resembles the real logon page.

Re:Issue 914451: Autofill does not respect autocomplete="off" by Dylan16807 on Sunday October 13, 2019 @01:06PM (#21241433)
If we had technology that doesn't exist, we could have secure biometrics.

In practice the computer is just getting a picture, which is semi-public information, and that's why the only thing you can rely on is that it's an identifier. It's not enough to authenticate when you really need security, only in more casual situations.

[dead]
Re:Issue 914451: Autofill does not respect autocomplete="off" by NeedMoreTea on Sunday October 13, 2019 @08:07AM (#21239945)
How many emails require a password to send to them? None. It's identifier. The password is the security.

Using biometrics - an identifier - for security as well is a compromise for convenience. As you say yourself biometrics make you who you are, they don't secure who you are.

Re:Issue 914451: Autofill does not respect autocomplete="off" by enriquepablo on Sunday October 13, 2019 @09:04AM (#21240155)
> The password ... is a way of identifying that you are you.

That is not correct. The "system" identifies you by your ID (username - biometrics - whatever). And for the system to ensure that whatever actions you perform on it, are really coming from you, you have to add proof of your identity to the orders for those actions. You use a secret to create that proof of identity. The secret is yours, the identity is the system's (what it uses to identify you).

If you use something you don't treat as a secret (such as your fingerprint) as your proof of identity, you'll be loosing it left and right - you'll be inviting everyone around to impersonate you. Drinking a can of coke and throwing it to the bin would be the same as printing your password in cards and passing them around.

Re:Issue 914451: Autofill does not respect autocomplete="off" by Santosh83 on Sunday October 13, 2019 @07:53AM (#21239903)
Anonymity is weakened if we tie authentication to biometrics. Something you know (as in password) is always theoretically more secure than something you are (your physical characteristics).
Re:Issue 914451: Autofill does not respect autocomplete="off" by scient on Sunday October 13, 2019 @09:19AM (#21240204)
I think the statement you make about "something you know" always being more secure is not nearly as clear cut as you present it.

A combination of "something you know" and "something you have" is always going to be a very strong authentication scenario, and making "something you have" a non-hackable thing that truly only you can have (i.e not a USB key or a TOTP seed etc.) is a good choice.

The catch here is that when you mention biometrics, you make the assumption of static biometrics (rightfully so, as most methods like Touch ID and Face ID are static), but if you combine lets say face biometrics with liveness checks, you are getting into a territory where faking them becomes much much more difficult (there are various mechanisms out there, the good ones rely on completely random interactions and light-bouncing detection methods as an example).

The real challenge is how do you make these very strong biometric methods frictionless and cheap? Or how do you introduce similar controls - like liveness - for easier methods like fingerprints?

And using any of these (ideally) has absolutely nothing to do with anonymity. You are not anonymous online regardless of what you use for authentication - and you are frankly not smart if you assume thats the case. A company offering a service with biometrics is no different from a company doing the same based on email/username and a password, if they do privacy and security right.

I could actually get into a much longer rant about this last part, as it blows my mind how many netizens are all about privacy and whatnot, yet are willing to expose every single detail about them when its convenient from them...

Re:Issue 914451: Autofill does not respect autocomplete="off" by Santosh83 on Sunday October 13, 2019 @10:17AM (#21240469)
> And using any of these (ideally) has absolutely nothing to do with anonymity. You are not anonymous online regardless of what you use for authentication - and you are frankly not smart if you assume thats the case. A company offering a service with biometrics is no different from a company doing the same based on email/username and a password, if they do privacy and security right.

Why should I use unchangeable, personally identifiable details when logging into some random joe's website? The mechanics of it are also tied to specific devices if I'm not wrong. I can't just login anywhere without risking leaking secrets. When did fingerprints, iris patterns and DNA go from necessary tools in law enforcement and biology (and for highly secure installations) into casual usage all over the place?

Re:Issue 914451: Autofill does not respect autocomplete="off" by dustinmoris on Sunday October 13, 2019 @12:09PM (#21241129)
You don't have to identify yourself with a "random Joe's website". You can read the comments here without identification, you can seach for flights without identifying yourself, you can search for hotels without giving away who you are, you can read the news, watch YouTube, etc.

But when you want to access something that should only belong to you, e.g. your bank account, your Google Drive files, your private emails, etc. then you must find a way of identifying yourself with given website. Username/password is one way, biometrics is another way.

Only my family has permission to enter my house. When someone enters my house who doesn't look like my family, then they can throw around all secrets, passwords and usernames they want, I'll kick them out, because in my eyes they don't pass the ultimate test of verification, namely biometrics.

So far we were unable to provide the same level of identificaiton via the web, but technology is changing rapidly, so I don't see why username/password are always going to be more secure. On a theoretical basis it doesn't make sense. Because inforation can be easily shared, spread and copied. My physical composition not.

Re:Issue 914451: Autofill does not respect autocomplete="off" by paulryanrogers on Sunday October 13, 2019 @01:26PM (#21241538)
Biometrics are digital interpretations, which can be copied. The biological sources cannot be easily changed. So _when_ the digital copies leak they become a liability.

Passwords can be easily changed. And until reliable, remote, mind reading technology becomes available they'll continue to be better than biometrics.

Re:Issue 914451: Autofill does not respect autocomplete="off" by enriquepablo on Sunday October 13, 2019 @09:33AM (#21240254)
> Anonymity is weakened if we tie authentication to biometrics.

I think you mean pseudonimity. There should be no authentication in anonimity.

> Something you know (as in password) is always theoretically more secure than something you are (your physical characteristics).

If you authenticate, you can use methods that are more or less secure. If you use a password method, and use a secret as password, it will be more secure than if you use a biometric as password.

But the security of the authentication method will bear no weight on the "pseudonimization" - meaning on the difficulty of linking the authenticated identity with your real, legal identity.

Re:Issue 914451: Autofill does not respect autocomplete="off" by Santosh83 on Sunday October 13, 2019 @09:36AM (#21240262)
It's effectively like using one password for every app/site authentication. What if the hashes/keys leak out? Then how easy would it be to change your keys for other sites while still using the same biometrics?
Re:Issue 914451: Autofill does not respect autocomplete="off" by dustinmoris on Sunday October 13, 2019 @07:56AM (#21239912)
Anonymity is of course weakened, but that is a different debate. Currently there is no anonymity at all if your account is linked to your email address, which you've also used to register your online banking account, your credit card verification, your PayPal account, etc. and when you have your mobile phone number confirmed, etc.

A password gives you 0 extra anonymity in this case. All it is used if for "identifycation" and in this regard it sucks in comparison to true biologial identification.

Re:Issue 914451: Autofill does not respect autocomplete="off" by cuu508 on Sunday October 13, 2019 @08:55AM (#21240116)
You are mixing up terminology. When logging in a website, your username identifies you, and your password authenticates you.
Re:Issue 914451: Autofill does not respect autocomplete="off" by Natanael_L on Sunday October 13, 2019 @09:14AM (#21240187)
Password authenticated key exchange algorithms (PAKE) solves the dictionary of secrets problem, by hiding the password from the server.
Re:Issue 914451: Autofill does not respect autocomplete="off" by cdubzzz on Sunday October 13, 2019 @09:42AM (#21240288)
We recently had to go through a website project and disable autocomplete on all password fields after a security scan as part of a PCI compliance process. For autofill password it didn’t seem to have any effect in _any_ browser I tested in. How can it be used to thwart password managers?
Re:Issue 914451: Autofill does not respect autocomplete="off" by driverdan on Sunday October 13, 2019 @10:12AM (#21240440)
Why would you need to disable autocomplete passwords for PCI compliance?
Re:Issue 914451: Autofill does not respect autocomplete="off" by toast0 on Sunday October 13, 2019 @12:39PM (#21241297)
Because either the PCI standard says so, or the PCI consultant says so.

PCI compliance is about checking boxes, not weighing the options and making good choices.

Re:Issue 914451: Autofill does not respect autocomplete="off" by cdubzzz on Sunday October 13, 2019 @12:49PM (#21241343)
Exactly this. Some of the checks _are_ valuable. We found a couple of real issues and made good security improvements. But we also ticked off more than a few boxes that made no damn real sense.