Bug 2189355 - [HPE 9.3 Bug] libxcrypt-compat inconsistently installed.
Summary: [HPE 9.3 Bug] libxcrypt-compat inconsistently installed.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libxcrypt
Version: 9.3
Hardware: aarch64
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Stanislav Zidek
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-24 23:16 UTC by Jerry Hoemann
Modified: 2023-07-31 09:00 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-03 09:30:45 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-10536 0 None None None 2023-05-02 15:02:34 UTC
Red Hat Issue Tracker CS-1572 0 None None None 2023-04-26 12:41:46 UTC
Red Hat Issue Tracker RHELPLAN-155592 0 None None None 2023-04-24 23:17:33 UTC

Description Jerry Hoemann 2023-04-24 23:16:38 UTC
Description of problem:

libxcrypt-compat is not being installed on Rhel 9.3 aarch64 where it is being installed with Rhel 9.3 x86_64.

I would have thought that the same set of libraries (sans architecture specific ones) would be installed for both x86 and aarch64.

I noticed the issue as the hpe ilorest command links against /usr/lib64/libcrypt.so.1 which is delivered as part of libxcrypt-comat.

From Bug #2034569, it appears that Rhel wants to deprecate this library for RHEL 10, but shouldn't it still be in Rhel 9.x?

I believe this issue exists on Rhel 9.2 as well.

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


How reproducible:


Steps to Reproduce:
1.Cold install from ISO
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Stanislav Zidek 2023-04-26 12:41:47 UTC
Hello, thanks for filing the bug. I confirm the behaviour you are describing. This is most probably not an issue in `libxcrypt` component though, so I filed a general CentOS Stream 9 request: https://issues.redhat.com/browse/CS-1572 Let's discuss it there if needed, I'll close this bug once it's confirmed it is not libxcrypt problem.

Comment 5 Stanislav Zidek 2023-05-03 09:30:45 UTC
After internal discussion, we decided that it is less desirable to bloat default installation with additional packages (than keeping default installation on various architectures consistent). "Workaround" should be pretty simple though, just make `libxcrypt-compat` an explicit dependency of the tool in question. I am using quotes because it is not really a workaround, just the correct thing to do anyway.


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