[Serdev] [Tracker] Created: (SER-219) radiusclient-ng2 errors on 64bit machines

[Tomasz Zieleniewski (JIRA)]

radiusclient-ng2 errors on 64bit machines
-----------------------------------------

                 Key: SER-219
                 URL: http://tracker.iptel.org/browse/SER-219
             Project: SER
          Issue Type: Bug
          Components: RADIUS
    Affects Versions: Ottendorf
         Environment: Debian OS etch Rel. with 64bits proc:AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
            Reporter: Tomasz Zieleniewski
            Priority: Critical


During the authentication procedure radiusclient-ng claims that secrets are incorrect with the message:
"received invalid reply digest from RADIUS server" on the recipient of the Accept from freeRadius, which was not true because they were for sure the same. probably radiusclient is doing MD5 incorrectly.
Another thing is the Access-Request send to radius where for instance service type which should be 4 bytes long is 8 bytes long as well as NAS-Port & NAS-IP-Address attributes which also should be 4
bytes of data, not 8:
rad_recv: Access-Request packet from host 127.0.0.1 port 32894,
id=198,
length=300 User-Name = "hellboy at voip.touk.pl"
        Digest-Attributes = 0x0a0968656c6c626f79
        Digest-Attributes = 0x010e766f69702e746f756b2e706c
        Digest-Attributes =
0x022a343562646565313636643534373338383937363231623565643437303833313236
61316461636633 Digest-Attributes =
0x04187369703a746f6d697840766f69702e746f756b2e706c
Digest-Attributes =
0x0308494e56495445
        Digest-Attributes = 0x050661757468
        Digest-Attributes = 0x090a3030303030303031
        Digest-Attributes =
0x08223639464435383136374435424646364631304633363746453943433138333339
Digest-Response = "2c8b62ee23ac6cbe4a551b8b698a509c"
        Service-Type = 0x0000000f00000000
        SER-Service-Type = 0x0000000300000000
        SER-Uri-User = "hellboy"
        NAS-Port = 0x000013c400000000
        NAS-IP-Address = 0x7f00000100000000

The same configuration works well on the 32bit CPU machine - this makes to suspect that problem is when running on a 64-bit system, and that the libradiusclient code isn't 64-bit clean.
There probably similar problem in openser which was solved with the following patch:
https://sourceforge.net/tracker/?func=detail&atid=743022&aid=1631052&group_id=139143

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.iptel.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira