> Thanks to members of these lists, I was able to get ESVA RADIUS 1.16 to
> compile on a DEC Alpha clone (Durango 433) running RH Linux 4.2. However,
> it won't authenticate anyone.
>
> I've spoken to Livingston tech support, and they think that the problem
> lies in passwd and RADIUS somehow using different versions of crypt. The
> system does have the latest rpm's installed from the factory. The only
> odd thing I can think of is that the passwd file came from an old Caldera
> CND 1.0 (x86) system and had to have pwconv5 run against it to implement
> shadow passwords.
>
> I've included a short debug session if that'll help. The line starting
> with LIVDEB: is demonstrating the differences between the way crypt sees
> the two passwords.
>
> radrecv: Request from host ffffffffd088e303 code=1, id=-120, length=76
> User-Name = "dbabst"
> Password = "\347Dn\265\276(\342\332\351\3151\267\016\251\302\323"
> Client-Id = 208.136.227.3
> Client-Port-Id = 6
> Received unknown attribute 61
> User-Service-Type = Framed-User
> Framed-Protocol = PPP
> PPP hint received
> LIVDEB: strcmp("hLzrpxGchI4H2", "hLhRfImIHEZdE"): FAILED
> Sending Reject of id -120 to ffffffffd088e303 (pm2.tcgcs.com)
I saw something about patches for a pam-enabled radius server. Maybe you
could check the archives, find that source, pull out that bit of code and
stick it in. Then you would be using the same authentication functions as
the system, and not do crypt yourself.
----------------------------------------------------------------------------
Steven P. Crain scrain@shore.net http://www.shore.net/~scrain
Shore.Net Unix Development and Administration
An ISP with Excellence in the Greater Boston Area.