Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
The crypt(3) man page states:
In the SHA implementation the entire key is significant
(instead of only the first 8 bytes in MD5).
This is incorrect. Both MD5 and SHA consider the entire key; it's DES that only uses the first 8 bytes.
This was fixed upstream in man-pages-3.25; see the attached patch.
Version-Release number of selected component (if applicable):
man-pages-3.22-12.el6
Additional info:
From the man-pages-3.25/Changes file:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
crypt.3
Petr Baudis
Correct note on key portion significance
As Marcel Moreaux notes:
The Linux manpage for crypt()[1] contains the following
statement as the last sentence of the NOTES section:
In the SHA implementation the entire key is significant
(instead of only the first 8 bytes in MD5).
It should probably say "DES" where it says "MD5" (and maybe
"MD5/SHA" where it says "SHA"), because in MD5 password hashing,
the entire key is significant, not just the first 8 bytes.
This patch fixes the wording.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0679.html
Description of problem: The crypt(3) man page states: In the SHA implementation the entire key is significant (instead of only the first 8 bytes in MD5). This is incorrect. Both MD5 and SHA consider the entire key; it's DES that only uses the first 8 bytes. This was fixed upstream in man-pages-3.25; see the attached patch. Version-Release number of selected component (if applicable): man-pages-3.22-12.el6 Additional info: From the man-pages-3.25/Changes file: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ crypt.3 Petr Baudis Correct note on key portion significance As Marcel Moreaux notes: The Linux manpage for crypt()[1] contains the following statement as the last sentence of the NOTES section: In the SHA implementation the entire key is significant (instead of only the first 8 bytes in MD5). It should probably say "DES" where it says "MD5" (and maybe "MD5/SHA" where it says "SHA"), because in MD5 password hashing, the entire key is significant, not just the first 8 bytes. This patch fixes the wording. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~