Bug 1264457

Summary: FreeRADIUS 3.0.4-6 miscalculates MPPE keys with TLS 1.2
Product: Red Hat Enterprise Linux 7 Reporter: Marcio <marcio.ota>
Component: freeradiusAssignee: Nikolai Kondrashov <nikolai.kondrashov>
Status: CLOSED ERRATA QA Contact: Jaroslav Aster <jaster>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: dpal, ebenes, jaster, pkis
Target Milestone: rcKeywords: TestOnly
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 20:36:03 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: 1202751    
Bug Blocks:    

Description Marcio 2015-09-18 13:45:09 UTC
Description of problem:
Same bug of FreeRADIUS 2.2.6 in RedHat el 6.

https://bugzilla.redhat.com/show_bug.cgi?id=1248484

Comment 2 Patrik Kis 2015-12-14 12:40:53 UTC
This bug report seems to be not correct.
It mentions FreeRADIUS 2.2.6 but it is filed against RHEL-7. Note that RHEL-7 contains FreeRADIUS version 3 and AFAIK this issue is not present there.

Comment 5 Patrik Kis 2016-02-12 13:52:09 UTC
IMHO this issue is not relevant for the currently shipped freeradius in RHEL-7 which is: freeradius-3.0.4

According to changelogs here http://freeradius.org/press/index.html#3.0.11
freeradius v3 TLS-1.2 support was added in version 3.0.5 and the issue reported here is fixed again in version 3.0.10.

Comment 10 Nikolai Kondrashov 2017-02-16 11:21:00 UTC
This should be fixed in 3.0.12.

Comment 11 Nikolai Kondrashov 2017-02-21 14:31:00 UTC
I think we should close this as NOTABUG (since the problem didn't exist in 3.0.4), once we verified this is not a problem in 3.0.12 either.

Comment 14 errata-xmlrpc 2017-08-01 20:36:03 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, 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/RHEA-2017:1954