Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Bug 828371 - Restrict Listening Interfaces for Postgres
Summary: Restrict Listening Interfaces for Postgres
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-04 17:26 UTC by james labocki
Modified: 2019-09-26 13:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-03 09:34:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description james labocki 2012-06-04 17:26:32 UTC
Description of problem:
Postgres listens on any network interface (5432/tcp), but is only used by localhost. Restricting it (especially since the username and password are well known) is important. Leaving it the way it is will fail any security audit.

Comment 1 Mike McCune 2012-06-13 15:28:08 UTC
I think this is solved with the katello-password command that is now in the latest release of Katello

Comment 2 Lukas Zapletal 2012-08-03 09:34:00 UTC
DONE UPSTREAM!

https://github.com/Katello/katello/pull/345


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