Parser for radius client config file is too strict.
Error is returned when radius client config file contains options which ppp's radius plugin can't recognize.
Configuration parser for radius client configuration now skips over directives which are unrecognized.
When configuration for authentication method based on radius is now populated from configuration file only known directives are considered while unknown are skipped without reporting errors in configuration.
Created attachment 691752 [details]
Patch to skip unrecognised directives when parsing radius file
If ppp is configured to use the radius plugin for authentication:
and radiusclient.conf contains 'bindaddr *' (as it does in radiusclient-ng-0.5.6-8.fc18.i686.rpm), then: authentication fails with these log messages:
> Nov 23 10:46:11 vucc2 pppd: /etc/radiusclient-ng/radiusclient.conf: line 75: unrecognized
> keyword: bindaddr
> Nov 23 10:46:11 vucc2 pppd: RADIUS: Can't read config file
The problem is that the config file parser in the radius plugin of pppd is too strict. Instead of ignoring configuration directives that it does not recognise, and does not care about, it stops parsing the file, and returns an error, and remains itself unconfigured.
Patch was long ago submitted to linux-ppp mailing list, but that list appears to be unmonitored by the ppp maintainers.
This is already fixed in fedora, fix maybe included in some future maintenance release of RHEL6.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
http://pkgs.devel.redhat.com/cgit/rpms/ppp/commit/?h=rhel-6.7&id=d911db69df67842eba1dcca3f60d6624def29da6 -> MODIFIED
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.