Anonymous | Login | 2024-12-21 23:56 MST |
Main | My View | View Issues | Change Log | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0018961 | ClearOS | app-radius - RADIUS Server | public | 2018-01-31 12:17 | 2018-05-01 12:05 | ||||
Reporter | cjones | ||||||||
Assigned To | dloper | ||||||||
Priority | normal | Severity | feature | Reproducibility | have not tried | ||||
Status | closed | Resolution | no change required | ||||||
Platform | OS | ClearOS | OS Version | ||||||
Product Version | 7.4.0 | ||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0018961: 'freeradius' needs to be updated | ||||||||
Description | This is a feature request to update 'freeradius'. Without this update, Windows 10 machines cannot authenticate using 'freeradius'. | ||||||||
Additional Information | https://support.microsoft.com/en-us/help/3121002/windows-10-devices-can-t-connect-to-an-802-1x-environment [^] | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Notes | |
(0007381) NickH (developer) 2018-04-10 03:43 |
I am not sure this bug is valid. M$ document says the fix refers to freeradius 3.0.7-3.0.9. ClearOS is at 3.0.13-8. The upstream change log, https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/doc/ChangeLog, [^] indicated this was fixed in 3.0.10 and Redhat rebased to upstream 3.0.10 on Wed Dec 09 2015 (see rpm -q --changelog freeradius) |
Issue History | |||
Date Modified | Username | Field | Change |
2018-01-31 12:17 | cjones | New Issue | |
2018-01-31 12:21 | dloper | Severity | minor => feature |
2018-01-31 12:21 | dloper | Assigned To | => dloper |
2018-01-31 12:21 | dloper | Status | new => assigned |
2018-04-10 03:43 | NickH | Note Added: 0007381 | |
2018-05-01 12:05 | user2 | Status | assigned => resolved |
2018-05-01 12:05 | user2 | Resolution | open => no change required |
2018-05-01 12:05 | user2 | Status | resolved => closed |