Re:JavaScript is now required to sign in to Google
by rocqua on Thursday November 01, 2018 @07:36AM
(#18352943)
Ip based lockouts as opposed to account based lockouts do better against cred stuffing. Because there is a cost to getting more IP adresses. Maybe carrier grade NAT would lead to too many false positives?
Re:JavaScript is now required to sign in to Google
by delroth on Thursday November 01, 2018 @07:47AM
(#18353020)
Most bad actors doing abuse at scale have access to large networks of proxies on residential or mobile IPs, usually backed by malware on workstations, laptops and mobile phones.
Even as a newcomer without the right contacts on the black market you can get started with very little upfront investment, using services like https://luminati.io/ (they pay software developers to bundle their proxy endpoints within their apps).
Re:JavaScript is now required to sign in to Google
by tinus_hn on Thursday November 01, 2018 @08:03AM
(#18353117)
IPv6 addresses aren’t really scarce.
Re:JavaScript is now required to sign in to Google
by delroth on Thursday November 01, 2018 @09:45AM
(#18353790)
/64 and /48 are pretty much on the same order of magnitude as IPv4s in terms of difficulty of acquisition, and I don't know why you would ever look at more than /64 when most major operating systems randomize the last 64 bits anyway (RFC4941).
Re:JavaScript is now required to sign in to Google
by astura on Thursday November 01, 2018 @09:54AM
(#18353860)
Cred stuffing is using botnets, you aren't going to have more than a couple login attempts per IP.
Re:JavaScript is now required to sign in to Google
by tinus_hn on Thursday November 01, 2018 @07:29AM
(#18352890)
I don’t see how JavaScript is anything more than a bandaid for that. The assumption is the attacker has the usercode and password combination and then you want to prevent him from logging in.
2FA is a good defence against it, but lockouts are less as they attacker will be going broad and not deep (could be a single request per user account)