Conversation
Add -fno-strict-aliasing for consistent behavior
umagmrit
requested review from
Gopal-Moolchandani,
aakashsingh2000,
ajju92,
ashwinsahu19,
chetanlanje74,
chitranshu198,
dasiyogesh,
preshitaagrawal,
silentsakky and
swathy-shaji
chetanlanje74
approved these changes
Apr 7, 2026
dasiyogesh
approved these changes
Apr 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue:
SHA256 and SSHA256 hashes generated by LDAP on RHEL9/Ubuntu22 systems are currently incorrect. This results in incorrect newly generated userPasswords, and authentication failure for valid SSHA256 hashed userPasswords generated by other systems (moved to R9 through migration/replication/etc. during OS upgrade process).
Fix:
Added
-fno-strict-aliasingto the SHA2 module build flags to prevent unsafe compiler optimizations.