-
-
Notifications
You must be signed in to change notification settings - Fork 196
Fix TOTP detection that are password fields (like HackerOne) #2333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Fix TOTP detection that are password fields (like HackerOne) #2333
Conversation
This needs to be validated for regressions before merging. |
@@ -1,7 +1,7 @@ | |||
'use strict'; | |||
|
|||
const ignoreRegex = /(bank|coupon|postal|user|zip).*code|comment|author|error/i; | |||
const ignoredTypes = [ 'email', 'password', 'username' ]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why password
was removed. Standard TOTP fields aren't password
fields, so this should be kept.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #2332 solution one, sometimes TOTP fields do have type=password
.
Another solution would be the second one (an explicit accept), then the type!=password
would also be bypassed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of making this change global, I'd suggest adding an exception for this site's TOTP detection to the sites.js
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of making this change global, I'd suggest adding an exception for this site's TOTP detection to the sites.js.
Fixes #2332