Bug #7170
closed
FreeRADIUS built-in certificate manager defaults to MD5 (!!!), no support for SHA2
Added by Kill Bill about 8 years ago.
Updated almost 8 years ago.
Affected Architecture:
All
Description
I'd rather nuke this redundant thing altogether, however not sure how to handle the transition for unfortunate users who might be using this.
- Assignee set to Anonymous
Guys, any ETA for 2.4 release (not date, but weeks/months, that sort of thing)? Would be a good opportunity to get rid of this, plus document required manual configuration changes in the release notes.
I agree, it could/should be killed for 2.4.
Not that far out, probably a few weeks.
FYI- I merged that PR, should be good to continue.
Thanks, can start killing some code now. :)
Merged.
Note: This needs to go to 2.4 release notes. Configuring the certs is no longer optional, it's simply a required configuration step for FreeRADIUS to work. Adding some file_notice() to freeradius_upgrade_config() plus an install message would be useful, I guess - see https://forum.pfsense.org/index.php?topic=128923.0
- Status changed from New to Feedback
- Status changed from Feedback to Resolved
- Assignee changed from Anonymous to Jim Pingle
This has all been removed from FreeRADIUS. Cert handling in FreeRADIUS is 100% done in the Cert Manager now on 2.3.4 and 2.4.
Also available in: Atom
PDF
Updated by Kill Bill 
Updated by 
Updated by