Bug 1277312
Summary: | Define types for port 9528 (used by openQA) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> |
Component: | selinux-policy | Assignee: | Zdenek Pytela <zpytela> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 35 | CC: | dominick.grift, dwalsh, jsedlak, lvrabec, mgrepl, plautrba |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-3.13.1-158.5.fc23 selinux-policy-3.13.1-158.6.fc23 selinux-policy-35.8-1.fc35 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-01-09 01:10:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Adam Williamson
2015-11-03 01:22:41 UTC
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. |