So I'm working on packaging openQA for Fedora ATM. openQA has its own daemon which runs on ports 9526 and 9527 (9527 for WebSockets) and it expects you to set up a regular web server (Apache or nginx) to reverse proxy it. (This style seems somewhat common for non-PHP webapps). Of course, that means the web server has to be allowed to connect to the daemon, something which is disallowed by default. It seems that policy modules cannot apply types to ports, so I need the distro policy to define types for these ports, if possible. Thanks! We'd also want a policy allowing web servers to connect to those ports, but I could ship that bit of policy in the openQA package if that would make more sense. If you want to see where these ports are specified: https://github.com/os-autoinst/openQA/blob/master/script/openqa https://github.com/os-autoinst/openQA/blob/master/script/openqa-websockets openQA is based on the Mojolicious framework, which uses the MOJO_LISTEN environment variable to decide what port to listen on; here, openQA is setting that variable to 9526 (openqa) or 9527 (openqa-websockets) so long as the admin hasn't overridden it when launching those scripts.
ping? folks?
echo...
Lukas can you give this bug a look?
Hi Adam, I can label for your these ports and then you can create own custom policy where you allow this rules for your needs. Do you agree? Names for ports 'openqa' and 'openqa-websockets' are fine to me.
yep, I plan to write a policy for the package, but the ports cannot be labelled in an external policy package, they have to be done in selinux-policy :) those names are fine, thanks!
selinux-policy-3.13.1-158.6.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-36a160982c
selinux-policy-3.13.1-158.6.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-36a160982c
selinux-policy-3.13.1-158.6.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Ooof, so I finally came back to implement the custom policy (yeah, just five years late, who's counting?) and now I find openQA is using one more port: 9528. Could that one get tagged too? It should be called 'openqa-liveviewhandler' or maybe just 'openqa-liveview'. It's used for a websockets connection for openQA's test development mode, see https://github.com/os-autoinst/openQA/blob/master/etc/apache2/vhosts.d/openqa-common.inc#L70 and https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/LiveHandler.pm . Thanks! The openQA servers are running on F35, so I only need this on F35+.
I've submitted a Fedora PR to address the issue: https://github.com/fedora-selinux/selinux-policy/pull/974
FEDORA-2022-decd9c4cae has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-decd9c4cae
FEDORA-2022-decd9c4cae has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-decd9c4cae` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-decd9c4cae See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Thanks a lot for this!
FEDORA-2022-decd9c4cae has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.