-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
p2p: allow comments in banlist files #9558
Conversation
255.255.255.0 # Saruman the White | ||
128.128.128.0 # Gandalf the Gray | ||
150.75.0.0 # Radagast the Brown | ||
99.98.0.0/16 # All of Misty Mountain | ||
|
||
# personal enemies | ||
1.2.3.4 # this woman used to give me swirlies | ||
6.7.8.9 # I just don't like the cut of his jib | ||
1.0.0.7#Literally James Bond, he wrecked my aston martin | ||
100.98.1.13 # Earl from HOA | ||
100.98.1.0/24 #The rest of the HOA for good measure |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Epic test file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW I don't have notes for my banlist on why some IP got banned
In-line comments explicitly explaining banned hosts/subnets might help assuage fears of some good banlists' arbitaryiness.
851d35e
to
b5f29ee
Compare
Rebased to apply this logic to the daemon command parser executor codepath as well. |
@jeffro256 release? |
In-line comments explicitly explaining banned hosts/subnets might help assuage fears of some good banlists' arbitaryiness.
@Boog900 @SyntheticBird45 @Rucknium