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 1530546 - Allow restricting TLS version in capsule
Summary: Allow restricting TLS version in capsule
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.4.0
Assignee: Stephen Benjamin
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-03 10:20 UTC by Tomer Brisker
Modified: 2021-06-10 14:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-16 18:54:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 21350 0 'Normal' 'Closed' 'Allow restricting TLS version' 2019-11-26 20:03:16 UTC

Description Tomer Brisker 2018-01-03 10:20:23 UTC
Comment 1 Tomer Brisker 2018-01-03 10:20:28 UTC 
Created from redmine issue http://projects.theforeman.org/issues/21350
Comment 2 Tomer Brisker 2018-01-03 10:20:34 UTC 
Upstream bug assigned to ehelms
Comment 4 Satellite Program 2018-01-03 17:27:53 UTC 
Upstream bug assigned to stbenjam
Comment 5 Satellite Program 2018-01-03 17:27:56 UTC 
Upstream bug assigned to stbenjam
Comment 6 Satellite Program 2018-01-03 21:28:04 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21350 has been resolved.
Comment 8 Mike McCune 2018-10-03 15:22:09 UTC 
VERIFIED for me.

similar to: https://bugzilla.redhat.com/show_bug.cgi?id=1553875#c5

NOTE: There are slightly different settings required for custom-heira.yaml on the Capsule, here is what I used:

# Foreman Proxy
foreman_proxy::tls_disabled_versions: ['1.0', '1.1']
foreman_proxy::ssl_disabled_ciphers: ['TLS_RSA_WITH_RC4_128_MD5', 'TLS_RSA_WITH_RC4_128_SHA']

# Dynflow
foreman_proxy::plugin::dynflow::ssl_disabled_ciphers: ['TLS_RSA_WITH_RC4_128_MD5', 'TLS_RSA_WITH_RC4_128_SHA']
foreman_proxy::plugin::dynflow::tls_disabled_versions: ['1.0', '1.1']

# Apache
pulp::ssl_protocol: "ALL -SSLv3 -TLSv1 -TLSv1.1 +TLSv1.2"
foreman_proxy_content::ssl_protocol:  "ALL -SSLv3 -TLSv1 -TLSv1.1 +TLSv1.2"
apache::mod::ssl::ssl_protocol: ['ALL', '-SSLv3', '-TLSv1', '-TLSv1.1', '+TLSv1.2']
apache::mod::ssl::ssl_cipher: '!aNULL:!eNULL:!LOW:!DES:!3DES:!RC4:!MD5:!EXP:!PSK:!SRP:!DSS:!ADH:HIGH'

#Tomcat
candlepin::tls_versions: ['1.2']

# QPID Dispatch
foreman_proxy_content::qpid_router_ssl_protocols: ['TLSv1.2']
foreman_proxy_content::qpid_router_ssl_ciphers: 'ALL:!aNULL:+HIGH:-SSLv3:!IDEA-CBC-SHA'


Before tuning in custom-heira.yaml

# for port in 9090 8008 8140 443 5000 8443; do echo $port:; nmap --script +ssl-enum-ciphers `hostname` -p $port| grep -e weak -e TLSv -e SSLv ; done

5647:
|   TLSv1.0: 
|       TLS_RSA_WITH_IDEA_CBC_SHA - weak
|   TLSv1.1: 
|       TLS_RSA_WITH_IDEA_CBC_SHA - weak
|   TLSv1.2: 
|       TLS_RSA_WITH_IDEA_CBC_SHA - weak
|_  least strength: weak
9090:
|   TLSv1.1: 
|   TLSv1.2: 
8008:
|   TLSv1.1: 
|   TLSv1.2: 
8140:
|   TLSv1.2: 
443:
|   SSLv3: No supported ciphers found
|   TLSv1.0: 
|   TLSv1.1: 
|   TLSv1.2: 
5000:
|   SSLv3: No supported ciphers found
|   TLSv1.0: 
|   TLSv1.1: 
|   TLSv1.2: 
8443:
|   TLSv1.1: 
|   TLSv1.2: 

After tuning:


# for port in 5647 9090 8008 8140 443 5000 8443; do echo $port:; nmap --script +ssl-enum-ciphers `hostname` -p $port| grep -e weak -e TLSv -e SSLv ; done
5647:
|   TLSv1.2: 
9090:
|   TLSv1.2: 
8008:
8140:
|   TLSv1.2: 
443:
|   SSLv3: No supported ciphers found
|   TLSv1.2: 
5000:
|   SSLv3: No supported ciphers found
|   TLSv1.2: 
8443:
|   SSLv3: No supported ciphers found
|   TLSv1.2:
Comment 10 Bryan Kearney 2018-10-16 18:54:56 UTC 
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/RHSA-2018:2927
Note You need to log in before you can comment on or make changes to this bug.