Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
In https://bugzilla.redhat.com/show_bug.cgi?id=1275246 various issues with redis have been fixed to make it work with SELinux.
Those fixes are based on the below commit:
> commit 368383855adeda55b57250ee196fb70e55e74ec8
> Author: Lukas Vrabec <lvrabec>
> Date: Thu Mar 17 16:28:30 2016 +0100
Problem is, that the fixes are missing two port definition that are required for redis to run correctly. Currently we have port 6379 specified. But the following ports are also required in certain use-case scenarios:
- 16379 redis cluster mode
- 26379 redis sentinel
This is based on the official redis documentation: http://redis.io/topics/quickstart#securing-redis
So if we could extend the patch from above and include port 26379 and 16379 as well, that would be greatly appreciated.
Version-Release number of selected component (if applicable):
- selinux-policy-3.13.1-80.el7
How reproducible:
always
Steps to Reproduce:
1. check if the policy does label port 26379 and 16379 as redis_port_t
Actual results:
[root@server ~]# semanage port -l | grep 6379
redis_port_t tcp 6379
[root@server ~]# semanage port -l | grep 26379
[root@server ~]# semanage port -l | grep 16379
[root@server ~]#
Expected results:
[root@server ~]# semanage port -l | grep 6379
redis_port_t tcp 6379
[root@server ~]# semanage port -l | grep 26379
redis_port_t
[root@server ~]# semanage port -l | grep 16379
redis_port_t
[root@server ~]#
Additional info:
Please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1275246 for more information as this was the initial trigger to get redis running with SELinux
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2283.html