News for hackers. Stuff that matters.

A comment on Bypassing Browser Security Warnings with Pseudo Password Fields. Parent comment

Re:Bypassing Browser Security Warnings with Pseudo Password ... by 3pt14159 on Thursday November 02, 2017 @11:03AM (#15611025)
There are situations where you need IPv4 due to rate-limiting. So while my stack technically supports IPv6 I have no reason to migrate to it.
[ Parent | on HN ]
Re:Bypassing Browser Security Warnings with Pseudo Password ... by andrewaylett on Thursday November 02, 2017 @05:15PM (#15614360)
You've been downvoted because this shouldn't be true, but since no-one else has stepped up, I'll bite :).

It's perfectly possible to do IP-based rate-limiting in the IPv6 world, you just need to do it based on different prefixes, rather than full IPs.

As a specific example, my ISP -- as is quite usual -- hands out /48s. So in the same way that you can rate limit my entire NAT'd IPv4 connection with a single entry, you can rate limit my entire IPv6 connection with a single entry, by storing the prefix.

[ Parent | on HN ]