Bug 1978216
Summary: | freeradius EAP methods with MS-CHAPv2 stopped worked with openssl-3.0 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Filip Dvorak <fdvorak> |
Component: | freeradius | Assignee: | Antonio Torres <antorres> |
Status: | CLOSED ERRATA | QA Contact: | Filip Dvorak <fdvorak> |
Severity: | medium | Docs Contact: | Josip Vilicic <jvilicic> |
Priority: | medium | ||
Version: | 9.0 | CC: | fdvorak, jherrman, jvilicic, nikolai.kondrashov, pasik, pcech |
Target Milestone: | beta | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | freeradius-3.0.21-24.el9 | Doc Type: | Bug Fix |
Doc Text: |
.MS-CHAP authentication with the OpenSSL legacy provider
Previously, FreeRADIUS authentication mechanisms that used MS-CHAP failed because they depended on MD4 hash functions, and MD4 has been deprecated in RHEL 9. With this update, you can authenticate FreeRADIUS users with MS-CHAP or MS-CHAPv2 if you enable the OpenSSL legacy provider.
If you use the default OpenSSL provider, MS-CHAP and MS-CHAPv2 authentication fails and the following error message is displayed, indicating the fix:
[literal]
----
Couldn't init MD4 algorithm. Enable OpenSSL legacy provider.
----
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-05-17 12:40:04 UTC | Type: | Bug |
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: | 2014525 | ||
Bug Blocks: |
Comment 24
Josip Vilicic
2022-05-13 23:54:10 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (new packages: freeradius), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:2371 |