We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It is possible to create funny rules for flowspec with, for example, a source IP as IPv4 and a destination IP as IPv6.
It is obviously not going to match any packets and should surely be reported to the user when the rule is created.
Should the implementation at the other end not validate input correctly, it may even be able to cause mayhem.
The same can be said about attributes (accepting binary) or updates in general.
The text was updated successfully, but these errors were encountered:
thomas-mangin
No branches or pull requests
It is possible to create funny rules for flowspec with, for example, a source IP as IPv4 and a destination IP as IPv6.
It is obviously not going to match any packets and should surely be reported to the user when the rule is created.
Should the implementation at the other end not validate input correctly, it may even be able to cause mayhem.
The same can be said about attributes (accepting binary) or updates in general.
The text was updated successfully, but these errors were encountered: