Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1433464 - SELinux prevent passenger_t from connecting to mysqldb_port_t
SELinux prevent passenger_t from connecting to mysqldb_port_t
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: selinux-policy (Show other bugs)
7.3
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Lukas Vrabec
Milos Malik
:
Depends On:
Blocks: 1393066
  Show dependency treegraph
 
Reported: 2017-03-17 13:11 EDT by Orion Poplawski
Modified: 2018-04-10 08:29 EDT (History)
6 users (show)

See Also:
Fixed In Version: selinux-policy-3.13.1-177.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 08:28:17 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 Product Errata RHBA-2018:0763 None None None 2018-04-10 08:29 EDT

  None (edit)
Description Orion Poplawski 2017-03-17 13:11:05 EDT
Description of problem:

type=AVC msg=audit(1489768671.674:182637): avc:  denied  { name_connect } for  pid=12843 comm="ruby" dest=3306 scontext=system_u:system_r:passenger_t:s0 tcontext=system_u:object_r:mysqld_port_t:s0 tclass=tcp_socket

However, default policy allows access to postgresql:

# sesearch -s passenger_t -p name_connect -A -C
   allow passenger_t postgresql_port_t : tcp_socket name_connect ;
   allow passenger_t http_port_t : tcp_socket name_connect ;

Seems like mysqld should be there too.

Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-102.el7_3.15.noarch
Comment 10 errata-xmlrpc 2018-04-10 08:28:17 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://access.redhat.com/errata/RHBA-2018:0763

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