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:
wpa_supplicant only supports MD4 hashes.
Version-Release number of selected component (if applicable):
wpa_supplicant-0.7.3-8.el6
How reproducible:
always
Steps to Reproduce:
1. Try to use a hash other than MD4 for the password entry
Actual results:
/etc/wpa_supplicant/wpa_supplicant.conf
only supports MD4 hashes for:
password=
----------
Sample: /etc/wpa_supplicant/wpa_supplicant.conf
Note: the credentials (identity and password lines) have been scrambled.
ctrl_interface=/var/run/wpa_supplicant
ap_scan=0
network={
key_mgmt=IEEE8021X
eap=PEAP
identity="user"
password=hash:0ec081f204654910186ebf3b4c79418b
eapol_flags=0
}
----------
Expected results:
Support for SHA256 (at least)
Support for SHA512 (additionally)
Additional info:
MD4 hash has been considered very insecure for many years.
Comment 4Beniamino Galvani
2016-11-09 17:51:38 UTC
The MSCHAPv2 standard requires MD4 hashing of the password and it's not possible to use a stronger algorithm. I'm closing this.
Description of problem: wpa_supplicant only supports MD4 hashes. Version-Release number of selected component (if applicable): wpa_supplicant-0.7.3-8.el6 How reproducible: always Steps to Reproduce: 1. Try to use a hash other than MD4 for the password entry Actual results: /etc/wpa_supplicant/wpa_supplicant.conf only supports MD4 hashes for: password= ---------- Sample: /etc/wpa_supplicant/wpa_supplicant.conf Note: the credentials (identity and password lines) have been scrambled. ctrl_interface=/var/run/wpa_supplicant ap_scan=0 network={ key_mgmt=IEEE8021X eap=PEAP identity="user" password=hash:0ec081f204654910186ebf3b4c79418b eapol_flags=0 } ---------- Expected results: Support for SHA256 (at least) Support for SHA512 (additionally) Additional info: MD4 hash has been considered very insecure for many years.