Skip to content
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

Remove entirely insecure configuration mode #23

Closed
wants to merge 1 commit into from
Closed

Remove entirely insecure configuration mode #23

wants to merge 1 commit into from

Conversation

job
Copy link
Contributor

@job job commented Mar 15, 2018

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

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
@job job closed this Dec 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

remove enforce_origin_in_as_set / enforce_prefix_in_as_set
1 participant