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

Blocklist mechanism #2

Open
2 tasks
maurerle opened this issue Jan 11, 2024 · 0 comments
Open
2 tasks

Blocklist mechanism #2

maurerle opened this issue Jan 11, 2024 · 0 comments

Comments

@maurerle
Copy link
Member

We currently do not have a blocklisting mechanism.
It might come in handy, if some nodes are behaving weird.

To do this, there should be an easy way to move a node to a quarantine domain or block it entirely.

Keys are typically added through this:
https://github.com/ffac/ff-supernode/blob/main/playbooks/roles/ff.wgbroker/templates/broker.py

  • changing the nodename leads to a different file name, this should be changed, to a way that duplicates in the public key are detected
  • there should be an easy mechanism to add keys to a quarantine or blocklist. Moving a key to a blocklist folder might be enough for the broker, but we have to see if the wg_link behaves fine with that as well
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

No branches or pull requests

1 participant