Hi,
Currently the rfc1918 bot does sanitize much more IPs than those mentioned in RFC1918 (5 rfcs or even more)
So it probably makes sense to rename the bot. Do you have suggestions? Or is RFC1918 well known as "the RFC with reserved IPs"?
And do you think it makes sense to make it more configurable? E.g. en/disable the sanitation for IPs and Domains separately?
Sebastian
On 11/15/2016 05:53 PM, Sebastian Wagner wrote:
And do you think it makes sense to make it more configurable? E.g. en/disable the sanitation for IPs and Domains separately?
To be more clear here: It's possible to configure the "policy" per field. But not per type of domain/ip. E.g drop only reserved TLDs (.invalid etc), or also first level domains (example.com etc). For IPs, this could be IPv4/IPv6, internal and reserverd IPs.
Am Dienstag 15 November 2016 17:53:18 schrieb Sebastian Wagner:
Currently the rfc1918 bot does sanitize much more IPs than those mentioned in RFC1918 (5 rfcs or even more)
So it probably makes sense to rename the bot.
+0.8
Do you have suggestions?
ignore-reserved reserved-ip-domain cleanout-special-ips-domains