Bug 241293 - Incorrect AccessRequest for mschap and mschap-v2 protocol
Summary: Incorrect AccessRequest for mschap and mschap-v2 protocol
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: radiusclient-ng
Version: 6
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jeffrey C. Ollie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 241294 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-05-24 21:09 UTC by Igor A Tarasov
Modified: 2008-02-07 05:01 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-07 05:01:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Igor A Tarasov 2007-05-24 21:09:23 UTC
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):
radiusclient-ng-0.5.2

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 = 127.0.0.1
        NAS-Port = 1
        Client-IP-Address = 127.0.0.1
This is incorrect, because there no MS-Chap-Challenge attribute for MS-CHAP 
request. 

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 = 
0x3d0092321c3e61197fdc418e730691cc350f0000000000000000ac9d910a28c5b9b839e9afa798919ad3b7d0be59a52e15e8
        NAS-IP-Address = 127.0.0.1
        NAS-Port = 1
        Client-IP-Address = 127.0.0.1

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 22:27:14 UTC
*** Bug 241294 has been marked as a duplicate of this bug. ***

Comment 2 Jeffrey C. Ollie 2007-05-25 20:49:57 UTC
I've updated the radiusclient-ng packages to 0.5.5.1 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
problem.

Comment 3 Jeffrey C. Ollie 2007-06-10 06:15:31 UTC
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 08:09:51 UTC
nothing change after update to 0.5.5.1
bugreport was posted to upstream developers too.

Comment 5 Jeffrey C. Ollie 2007-06-11 04:45:17 UTC
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 04:49:29 UTC
Nevermind, I found the report...

http://developer.berlios.de/bugs/?func=detailbug&bug_id=11175&group_id=1208

Comment 7 Jeffrey C. Ollie 2008-02-07 05:01:47 UTC
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.