2222665 – Connect pcsd TLS configuration to RHEL crypto policies

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 2222665 - Connect pcsd TLS configuration to RHEL crypto policies

Summary: Connect pcsd TLS configuration to RHEL crypto policies

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 9
Classification:	Red Hat
Component:	pcs
Sub Component:
Version:	9.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	medium
Severity:	medium
Target Milestone:	rc
Target Release:	9.4
Assignee:	Tomas Jelinek
QA Contact:	cluster-qe
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2023-07-13 11:53 UTC by Tomas Jelinek
Modified:	2023-09-22 20:26 UTC (History)
CC List:	7 users (show)
Fixed In Version:
Doc Type:	Release Note
Doc Text:	Previously, pcsd TLS cipher list was by default set to 'DEFAULT:!RC4:!3DES:@STRENGTH'. With this update, the cipher list is by default defined by system-wide crypto policy. Based on the currently set crypto policy, the TLS ciphers accepted by pcsd may change when upgrading to this version of pcs. See 'man crypto-policies' for more information about crypto policies framework.
Clone Of:
Environment:
Last Closed:	2023-09-22 20:26:41 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:
Flags:	pm-rhel: mirror+

Attachments	(Terms of Use)

Links
System	ID	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHEL-7724	None	Migrated	None	2023-09-22 20:26:50 UTC
Red Hat Issue Tracker	RHELPLAN-165529	None	None	None	2023-08-10 15:46:17 UTC
Red Hat Issue Tracker	RHELPLAN-165530	None	None	None	2023-08-10 15:46:12 UTC

Description Tomas Jelinek 2023-07-13 11:53:57 UTC

Description of problem:
Currently, it is possible to configure TLS ciphers and other options used by pcsd in /etc/sysconfig/pcsd. There is a default value hardcoded in pcsd source. RHEL (and Fedora) provides a system-wide crypto policies framework, which allows to configure TLS settings in one place for the entire OS and all applications. This has a benefit of easy management, when disabling a weak cipher can be done in a single place. Pcsd should connect to this framework.


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


How reproducible:
always, easily


Steps to Reproduce:
1. update-crypto-policies --set DEFAULT
2. nmap -p 2224 {pcsd node} --script +ssl-enum-ciphers
3. update-crypto-policies --set FIPS
4. nmap -p 2224 {pcsd node} --script +ssl-enum-ciphers


Actual results:
TLS ciphers used by pcsd do not depend on the current crypto policy


Expected results:
TLS ciphers used by pcsd are set by the current crypto policy


Additional info:
nmap-7.91-12.el9 doesn't show TLSv1.3, use nmap-7.93-2.fc38


Proposed solution:
Make 'PROFILE=SYSTEM' the default for PCSD_SSL_CIPHERS

Comment 2 Tomas Jelinek 2023-08-31 08:20:55 UTC

Upstream patch: https://github.com/ClusterLabs/pcs/commit/74d9e0059cf3495538d2b5a2c169a6896b77cba8

Test:
[root@rh92-node1:~]# update-crypto-policies --set DEFAULT
Setting system policy to DEFAULT
Note: System-wide crypto policies are applied on application start-up.
It is recommended to restart the system for the change of policies
to fully take place.
[root@rh92-node1:~]# systemctl restart pcsd
[root@fed38-node1:~]# nmap -p 2224 rh92-node1 --script +ssl-enum-ciphers
Starting Nmap 7.93 ( https://nmap.org ) at 2023-08-31 09:52 CEST
Nmap scan report for rh92-node1 (192.168.122.12)
Host is up (0.00039s latency).
rDNS record for 192.168.122.12: rh92-node1.vm

PORT     STATE SERVICE
2224/tcp open  efi-mg
| ssl-enum-ciphers:
|   TLSv1.2:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (secp256r1) - A
|     compressors:
|       NULL
|     cipher preference: server
|   TLSv1.3:
|     ciphers:
|       TLS_AKE_WITH_AES_256_GCM_SHA384 (secp256r1) - A
|       TLS_AKE_WITH_AES_128_GCM_SHA256 (secp256r1) - A
|       TLS_AKE_WITH_AES_128_CCM_SHA256 (secp256r1) - A
|     cipher preference: server
|_  least strength: A
MAC Address: 52:54:00:90:01:09 (QEMU virtual NIC)

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

[root@rh92-node1:~]# update-crypto-policies --set FIPS
Setting system policy to FIPS
Note: System-wide crypto policies are applied on application start-up.
It is recommended to restart the system for the change of policies
to fully take place.
[root@rh92-node1:~]# systemctl restart pcsd
[root@fed38-node1:~]# nmap -p 2224 rh92-node1 --script +ssl-enum-ciphers
Starting Nmap 7.93 ( https://nmap.org ) at 2023-08-31 09:54 CEST
Nmap scan report for rh92-node1 (192.168.122.12)
Host is up (0.00023s latency).
rDNS record for 192.168.122.12: rh92-node1.vm

PORT     STATE SERVICE
2224/tcp open  efi-mg
| ssl-enum-ciphers:
|   TLSv1.2:
|     ciphers:
|       TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (secp256r1) - A
|       TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (secp256r1) - A
|     compressors:
|       NULL
|     cipher preference: server
|   TLSv1.3:
|     ciphers:
|       TLS_AKE_WITH_AES_256_GCM_SHA384 (secp256r1) - A
|       TLS_AKE_WITH_AES_128_GCM_SHA256 (secp256r1) - A
|       TLS_AKE_WITH_AES_128_CCM_SHA256 (secp256r1) - A
|     cipher preference: server
|_  least strength: A
MAC Address: 52:54:00:90:01:09 (QEMU virtual NIC)

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

List of pcsd ciphers have changed based on the selected crypto-policy

Comment 3 RHEL Program Management 2023-09-22 20:24:21 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-22 20:26:41 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 "RHEL-" 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.

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