Throttle IPv6 signup for subnet #17588
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
About 20 minutes ago, a large amount of IPv6 spambots occurred in my instance.
|
Some even /56 but are there smaller ones? If so this could limit people on those. |
Gargron
approved these changes
Feb 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, Mastodon throttle signup 25/5min per specific IP
Unlike IPv4, IPv6 address is very different. For an example, Cloud VPS providers give entire /64 subnet to a single server.
So this PR raise the bar using 64 bit netmask. while it is narrow enough compare to IPv4(=32bit mask)