News for hackers. Stuff that matters.
Re:JavaScript is now required to sign in to Google by lisper on Wednesday October 31, 2018 @11:44PM (#18351315)
> Throttle based on what?

User Id?

Re:JavaScript is now required to sign in to Google by gyaru on Thursday November 01, 2018 @06:59AM (#18352686)
That's a terrible idea. Back when MSN was one of the most common instant messengers, there was a common prank that was called "freezing" where you just continuously kept trying to log into someones account and it would lock itself out for 15mins or more depending how long you kept doing it.

There was automated tools that did this too!

Re:JavaScript is now required to sign in to Google by Too on Thursday November 01, 2018 @01:35AM (#18351679)
That's the first obvious countermeasure and will prevent hackers targeting a specific account. But there are other ways to crack passwords, one is to try the same password but iterate over user ids instead. As hackers would start with the most common password you can't throttle globally on same password attempts either because well yeah, it is by definition the most commonly used one which should have a lot of traffic.
Re:JavaScript is now required to sign in to Google by QasimK on Thursday November 01, 2018 @04:30AM (#18352132)
Google can ban common passwords, or passwords that look like they’re being targeted (over the long-run).
Re:JavaScript is now required to sign in to Google by sdjhksgsdfsaa on Tuesday November 06, 2018 @05:55PM (#18395631)
This has nothing to do with anything but I don't know how else to get in touch with you. Could you upload your zero spam email setup guide somewhere? Your site was hacked so the link I had doesn't work:

http://iamqasimk.com/2016/10/16/absolutely-zero-email-spam/

Re:JavaScript is now required to sign in to Google by QasimK on Sunday November 11, 2018 @06:54PM (#18429528)
I’m sorry, I changed the domain to QasimK.io, but neglected to set up forwarding. I will do that.

http://qasimk.io/2016/absolutely-zero-email-spam/

Re:JavaScript is now required to sign in to Google by michaelt on Thursday November 01, 2018 @05:34AM (#18352342)
"Credential stuffing" as I've heard it used refers to taking username/password combos from one breached site and trying them in other sites.

So for example LinkedIn has a breach, which reveals to evildoers that user '[email protected]' uses the password 'smith1234' then they test that username and password in Amazon, Netflix, Steam and so on.

They only make one attempt per account, because they only have one leaked password per account. Hence, throttling per account isn't an option.

Re:JavaScript is now required to sign in to Google by lewiscollard on Thursday November 01, 2018 @02:12AM (#18351754)
That would create an easy denial of service attack: if I wanted to deny you access to your account I'd spam it with bad login attempts.
Re:JavaScript is now required to sign in to Google by homero on Thursday November 01, 2018 @02:51AM (#18351835)
Happens weekly to my Sears account.
Re:JavaScript is now required to sign in to Google by ryantriangles on Thursday November 01, 2018 @12:15AM (#18351412)
With credential stuffing, isn't it unlikely the perpetrator wants to make more than one or two attempts per user ID?