-
Notifications
You must be signed in to change notification settings - Fork 6
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
Firewall rules #9
Comments
It's great idea, I'll research that! |
It seems that gnome-network-displays adds new firewalld zone automatically: https://gitlab.gnome.org/GNOME/gnome-network-displays/-/issues/134 |
But they are changing to that new zone at runtime if it isn't enabled. |
Yeah, I see what they are doing there. They indeed expect the zone to be there and in case it is not, they create it. It seems that they operate on fixed port. The interface they use to communicate with the firewalld is D-Bus. We could do the same, since there are pretty good D-Bus bindings for Rust, however there are is a gotcha here:
Having said that, I'll run some tests with my local firewalld and see if there are any potential problems. |
@sp1ritCS I'm not quite done with the code yet, but it would be great if you could take a look at this PR and particularly firewall module. I implemented adding mdns service and fixed Dragit port in case it's not available in runtime config. |
Closing the issue. The next release (including Flatpak) will contain the change! |
Is it possible for dragit to automatically punch holes into firewalld, if it has to listen to a specific port?
I know that gnome-network-displays are doing something like this, might be a good idea to look at them and how they do it.
The text was updated successfully, but these errors were encountered: