The same problem in rhel6, checked with freeradius-2.1.12-4.el6_3
+++ This bug was initially created as a clone of Bug #1099625 +++
Description of problem:
The default_md field in the /etc/raddb/certs/client.cnf, /etc/raddb/certs/ca.cnf, and /etc/raddb/certs/server.cnf default to sha1. At this point they should probably default to sha256 since it's been deemed that both md5 and sha1 are not secure.
Version-Release number of selected component (if applicable):
--- Additional comment from John Dennis on 2014-05-20 15:45:44 EDT ---
Valid point, we already had patched the cnf file from upstream to move from md5 to sha1 a few years back. Upgrading to sha256 is good next step in the ever evolving cipher hardening.
FWIW these files are meant to be temporary *example* certs uesd just to get started (we reduce the validity period just to reinfoce that idea) and our documentation clearly states you're supposed to acquire better certs in any real deployment. However the example should "lead by example" and indeed we should bump up the digest algorithm. Just saying this to avoid this being construed as a serious security issue.
--- Additional comment from Nikolai Kondrashov on 2014-07-16 14:58:37 EDT ---
Fix merged upstream: https://github.com/FreeRADIUS/freeradius-server/pull/734
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.