Bug 2225253

Summary: [RFE]: TLS 1.3 Support for Candlepin in Satellite 6
Product: Red Hat Satellite Reporter: Ganesh Payelkar <gpayelka>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.14.0CC: ahumbe, dhjoshi, ehelms, nmoumoul, rlavi, saydas
Target Milestone: UnspecifiedKeywords: FutureFeature, MigratedToJIRA, Security, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:25:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ganesh Payelkar 2023-07-24 18:49:36 UTC
Description of problem:

[RFE]: TLS 1.3 Support for Candlepin in Satellite 6

Version-Release number of selected component (if applicable):
satellite-6.14.0-3.el8sat.noarch
candlepin-4.3.1-1.el8sat.noarch

How reproducible:
New installation

Steps to Reproduce:

1. Install the latest version of satellite 6 on RHEL 8
2. Test the connection through openssl/Curl/nmap



Actual results:

# nmap --script +ssl-enum-ciphers localhost -p 23443

PORT      STATE SERVICE
23443/tcp open  unknown
| ssl-enum-ciphers: 
|   TLSv1.2: 
|     ciphers: 
|       TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (secp256r1) - A
|     compressors: 
|       NULL
|     cipher preference: client
|     warnings: 
|       Key exchange (secp256r1) of lower strength than certificate key
|_  least strength: A

Nmap done: 1 IP address (1 host up) scanned in 0.50 seconds


# curl --tlsv1.3 -v https://localhost:23443/candlepin --cacert /etc/pki/katello/certs/katello-default-ca.crt
*   Trying ::1...
* TCP_NODELAY set
* connect to ::1 port 23443 failed: Connection refused
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 23443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/pki/katello/certs/katello-default-ca.crt
  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS alert, protocol version (582):
* error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol version
* Closing connection 0
curl: (35) error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol version


[root@vm255-136 ~]# openssl s_client -connect localhost:23443 -tls1_3 -CAfile /etc/pki/katello/certs/katello-default-ca.crt
CONNECTED(00000003)
139807602083648:error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol version:ssl/record/rec_layer_s3.c:1544:SSL alert number 70
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 240 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---

Expected results:


Additional info:

The expectation for the Request for Enhancement (RFE) to add TLS 1.3 support in candlepin
TLS 1.3 is the latest version of the TLS protocol and offers enhanced security and performance benefits over earlier versions. The expectation is that supporting TLS 1.3 will improve the overall security posture of Foreman Proxy and Satellite 6.


# /usr/sbin/tomcat version
Server version: Apache Tomcat/9.0.50
Server built:   Jun 24 2022 20:49:41 UTC
Server number:  9.0.50.0
OS Name:        Linux
OS Version:     4.18.0-240.el8.x86_64
Architecture:   amd64
JVM Version:    17.0.8+7-LTS
JVM Vendor:     Red Hat, Inc.

Comment 2 Nikos Moumoulidis 2023-07-31 15:11:45 UTC
TLS configuration of tomcat (as well as all tomcat configuration) is done at the Installer component, not the candlepin component itself, so moving to Installer.

Comment 3 Eric Helms 2024-06-06 16:25:13 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.