Bug 2359082
| Summary: | SIGILL from libcrypto.so.3.5.0 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dan Horák <dan> |
| Component: | openssl | Assignee: | Dmitry Belyavskiy <dbelyavs> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | crypto-team, dbelyavs, mspacek, mturk, praiskup, shebburn, suraj.ghimire7, tm |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | ppc64le | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openssl-3.5.0-3.fc43 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-04-16 17:24:58 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1071880 | ||
|
Description
Dan Horák
2025-04-11 12:37:01 UTC
Could you please report this issue upstream? Our downstream patches don't touch assembler code ack, will do *** Bug 2359744 has been marked as a duplicate of this bug. *** Could you please try this build if the infrastructure wakes up https://koji.fedoraproject.org/koji/taskinfo?taskID=131563912 no more a SIGILL as far as I can tell, what change did you made? A build without this flag "enable-ec_nistp_64_gcc_128", as proposed in https://github.com/openssl/openssl/issues/27350 If you have anyone who knows ppc64le asm, it would be great to implement a proper fix - otherwise it would stay vulnerable to side-channel attacks (fixing them introduced this issue) FEDORA-2025-c31309a82b (openssl-3.5.0-3.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-c31309a82b (In reply to Dmitry Belyavskiy from comment #6) > A build without this flag "enable-ec_nistp_64_gcc_128", as proposed in > https://github.com/openssl/openssl/issues/27350 for the record, we need this change only in Fedora, RHEL 9+ requires Power9 or newer, so it's safe with the new implementation > If you have anyone who knows ppc64le asm, it would be great to implement a > proper fix - otherwise it would stay vulnerable to side-channel attacks > (fixing them introduced this issue) I will ask in the community, but it will be tough as it needs both Power ISA and security expertise ... And as I am not familiar with OpenSSL code, do you think it's possible to change OpenSSL in a way that the new safe implementation would be selected during runtime when Power9+ CPU is detected and and the unsafe one for Power8 (it's EOL hw anyway)? I believe OpenSSL is generally capable of such runtime selection. Probably this check should be made more strict:
if (OPENSSL_ppccap_P & PPC_MADD300)
see man openssl-env for slightly more details
FEDORA-2025-c31309a82b (openssl-3.5.0-3.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. |