Red Hat Bugzilla – Bug 136652
RADIUS and MS-CHAP V2 support
Last modified: 2007-11-30 17:10:52 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera
Description of problem:
here is a long awaited patch for RADIUS support for pppd. It works
for us for about 2 years!
I also added a patch for MS-CHAP V2 authentification, if you are
happy with the license, please also apply it. It also works for us in
combination with pptpd.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
It's a feature request.
Created attachment 105587 [details]
The RADIUS patch.
On 14 November 2004 ppp 2.4.3 was released.
It include things like:
* Various fixes and enhancements to the radius and rp-pppoe plugins
have been added.
* There is a new winbind plugin, from Andrew Bartlet of the Samba
team, which provides the ability to authenticate the peer against an
NT domain controller using MS-CHAP or MS-CHAPV2.
* There is a new pppoatm plugin, by various authors, sent in by David
So maybe updating ppp to newer version will resolve this bug?
If you will be updating ppp please add to spec file URL to home page:
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Closing per lack of response to previous request for information. This bug was
originally filed against a much earlier version of Fedora Core, and significant
changes have taken place since the last version for which this bug is confirmed.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.