-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add ability to blacklist certain keys #38
Comments
I'm guessing easiest thing to do is create a new API for an in-memory list of keys/clients you want to block, and check this list before calling MQTT: https://github.com/freifunkMUC/wgkex/blob/main/wgkex/broker/app.py#L77 |
My idea was to read a It would be cool if the file is occassionally checked for changes and reloaded to memory. But also just a static file which is read on start of the broker is fine. My prefered format would be:
But reason is optional and we put this in the answer to the client. |
Then I think solving this first is the correct thing to do: #39 |
I created a first draft to block keys on the client side in #76 . I'll go about looking at trying to get keys back out of the worker to the broker so we avoid duplication. |
Add a (temporary) blacklist feature to the daemon. This is needed in case some abusive client wants to connect. Then we just reject the Wireguard key and don't send it to MQTT.
The text was updated successfully, but these errors were encountered: