Bug 1493285 – selinux port context ldap_port_t

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1493285 - selinux port context ldap_port_t

Summary:	selinux port context ldap_port_t

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	selinux-policy (Show other bugs)
Sub Component:
Version:	7.4
Hardware:	All Linux

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Lukas Vrabec
QA Contact:	Milos Malik
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-09-19 15:49 EDT by unixops
Modified:	2018-04-10 08:44 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	selinux-policy-3.13.1-175.el7
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-04-10 08:43:43 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:0763	None	None	None	2018-04-10 08:44 EDT

Groups: None (edit)

Description unixops 2017-09-19 15:49:59 EDT

Description of problem:
The ldap_port_t context contains the following TCP ports:
389, 636, 3268, 7389

However, port 3269 should also be added. This is the encrypted Global Catalog port LDAP port, the encrypted version of port 3268.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. sudo semanage port -l | grep ldap_port_t
2.
3.

Actual results:
ldap_port_t                    tcp      389, 636, 3268, 7389


Expected results:
ldap_port_t                    tcp      389, 636, 3268, 3269, 7389


Additional info:

Comment 7 errata-xmlrpc 2018-04-10 08:43:43 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.