by makepanic on 12/20/22, 9:44 AM with 95 comments
by pontilanda on 12/20/22, 12:25 PM
Depending on the exact wording, I completely expect the browser to suggest the same password for the same website in the same session for the same user.
Websites are crap and sometimes you need to enter the same password twice before the browser has gotten the notice to actually save the first one.
by TrianguloY on 12/20/22, 12:41 PM
This will change the ui a bit though.
by dncornholio on 12/20/22, 12:23 PM
by jonnycomputer on 12/20/22, 12:12 PM
https://bugzilla.mozilla.org/show_bug.cgi?id=1786712
This is sort of a ridiculous bug, tbh. What rationale could this be "currently by design"?
by makepanic on 12/20/22, 9:45 AM
by SahAssar on 12/20/22, 11:45 AM
by turtleman1338 on 12/20/22, 11:55 AM
What?
by jmclnx on 12/20/22, 12:39 PM
tr -cd "[:alnum:]" < /dev/urandom | fold -w 20 | sed 10q
So I have no need for these fancy password generators :)
by bakhy on 12/20/22, 12:18 PM
IMO they should just remove the password generator feature. It's barely usable, and with this behavior it's just dangerous.
Why barely usable? Some really simple features are missing. I miss the ability to specify password requirements - for annoying sites which specify length, require so and so many these and those types of characters, or even forbid some types. And another one is that it's not possible to manually generate a password, not even in the password storage UI, when manually adding a new entry. So, if a site did not correctly declare a password field, which happens, you must generate a password yourself somehow.
by sys42590 on 12/20/22, 11:53 AM
If that's the case it would make a new "named" vulnerability (FOXHOLE, FIREBLEED, whatever).