Remove entirely insecure configuration mode #23
Closed
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.
In order to protect both IXP operator and IXP participants, we should
ensure that using arouteserver never leads to an insecure mode of
operation.
While arouteserver should offer a degree on flexibility in terms of
fine tuning what IRRs are used, whether ARIN WHOIS or RPKI is used
or not - there should not be a configuration path that leads to no
filters at all. Offering fully insecure modes is not user friendly.
This fixes #22