Bug 241293 - Incorrect AccessRequest for mschap and mschap-v2 protocol
Incorrect AccessRequest for mschap and mschap-v2 protocol
Product: Fedora
Classification: Fedora
Component: radiusclient-ng (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Jeffrey C. Ollie
Fedora Extras Quality Assurance
: Reopened
: 241294 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2007-05-24 17:09 EDT by Igor A Tarasov
Modified: 2008-02-07 00:01 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-02-07 00:01:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Igor A Tarasov 2007-05-24 17:09:23 EDT
Description of problem:
Radiusclient use incorrect AccessRequest for mschap and mschap-v2 protocol to 
authenticate against Radius Server. But old versions working fine.

Version-Release number of selected component (if applicable):

How reproducible:
Cannot use MS-CHAP or MS-CHAP-V2 protocol to authenticate user. Other 
protocols (PAP and CHAP) working correct.

Steps to Reproduce:
1. Try to authenticate with ms-chap protocol
Actual results:
Dump of packet by freeradius:
Packet-Type = Access-Request
        Service-Type = Framed-User
        Framed-Protocol = PPP
        User-Name = "dicr"
        NAS-IP-Address =
        NAS-Port = 1
        Client-IP-Address =
This is incorrect, because there no MS-Chap-Challenge attribute for MS-CHAP 

Expected results:
Old version libradiusclient 0.3.1 work fine with the next packet dump:
Packet-Type = Access-Request
        Service-Type = Framed-User
        Framed-Protocol = PPP
        User-Name = "dicr"
        MS-CHAP-Challenge = 0x1e9cc0ca7c6a1e9e4bb40c89fc2142ff
        MS-CHAP2-Response = 
        NAS-IP-Address =
        NAS-Port = 1
        Client-IP-Address =

Additional info:
With PAP and CHAP protocol it working fine, including UserPassword or 
ChapChallenge and ChapPassword attributes, but MS-CHAP request is malformed 
and not correct. Freeradius say "No UserPassword attribute" and refuse 
authentication, but with old version libradiusclient all working fine..
Comment 1 Jeffrey C. Ollie 2007-05-24 18:27:14 EDT
*** Bug 241294 has been marked as a duplicate of this bug. ***
Comment 2 Jeffrey C. Ollie 2007-05-25 16:49:57 EDT
I've updated the radiusclient-ng packages to plus a couple of patches
that were in the upstreams CVS.  If the new packages don't fix the problem
you'll need to work with the upstream developers to figure out a solution to the
Comment 3 Jeffrey C. Ollie 2007-06-10 02:15:31 EDT
Since I haven't seen a reply I'm going to assume that the problem was fixed and
close this bug.  Reopen if the bug if you are still having problems.
Comment 4 Igor A Tarasov 2007-06-10 04:09:51 EDT
nothing change after update to
bugreport was posted to upstream developers too.
Comment 5 Jeffrey C. Ollie 2007-06-11 00:45:17 EDT
Please put a link to the upstream bugreport in a comment, so that anyone else
that encounters this bug can follow the upstream work.
Comment 6 Jeffrey C. Ollie 2007-06-11 00:49:29 EDT
Nevermind, I found the report...

Comment 7 Jeffrey C. Ollie 2008-02-07 00:01:47 EST
radiusclient-ng has been at version 0.5.6 for a while, and the upstream bug
hasn't been updated.   I'm going to close this bug for now until upstream can
provide a fix.

Note You need to log in before you can comment on or make changes to this bug.