Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1348471 - Additional ports required in selinux-policy for redis
Additional ports required in selinux-policy for redis
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy (Show other bugs)
7.2
x86_64 Linux
high Severity high
: rc
: 7.3
Assigned To: Lukas Vrabec
Milos Malik
:
Depends On:
Blocks: 1203710
  Show dependency treegraph
 
Reported: 2016-06-21 05:09 EDT by Simon Reber
Modified: 2016-11-03 22:32 EDT (History)
7 users (show)

See Also:
Fixed In Version: selinux-policy-3.13.1-81.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-03 22:32:16 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2435021 None None None 2016-07-11 03:46 EDT
Red Hat Product Errata RHBA-2016:2283 normal SHIPPED_LIVE selinux-policy bug fix and enhancement update 2016-11-03 09:36:25 EDT

  None (edit)
Description Simon Reber 2016-06-21 05:09:28 EDT
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@redhat.com>
> 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
Comment 6 errata-xmlrpc 2016-11-03 22:32:16 EDT
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

Note You need to log in before you can comment on or make changes to this bug.