Problem with crypt passwords matching

2012-08-15 Thread Robert Haskins
I am running Freeradius 2.1.12 on a Centos box. I am able to authenticate from the server command line, and from a Cisco ASR1k BRAS via the command line. However, when I attempt to authenticate customers from the DSL network, I get a reject, even though the crypt'd passwords match! Here is a

Re: Problem with crypt passwords matching

2012-08-15 Thread alan buxey
Hi, ++[unix] returns updated okay...so I assume you have edited the passwd module to read thew shadow file? [files] users: Matched entry DEFAULT at line 169 [files] users: Matched entry DEFAULT at line 172 [files] users: Matched entry DEFAULT at line 186 what do these lines have/say?

Re: Problem with crypt passwords matching

2012-08-15 Thread Robert Haskins
What do you mean by editing the passwd module? As for the users lines, here is what is in that file (first line is 169 and the last one is 186): DEFAULT Auth-Type == System Fall-Through == 1 DEFAULT Service-Type == Framed-User Framed-IP-Address == 255.255.255.254,

Re: Problem with crypt passwords matching

2012-08-15 Thread Fajar A. Nugraha
On Thu, Aug 16, 2012 at 3:40 AM, Robert Haskins robert.hask...@gmail.com wrote: I get a reject, even though the crypt'd passwords match! That's not how crypt works. You don't compare the crypted password. [pap] login attempt with password krt444 that is what the user sends [pap] Using

Re: Problem with crypt passwords matching

2012-08-15 Thread Doug Hardie
On 15 August 2012, at 14:23, Fajar A. Nugraha wrote: On Thu, Aug 16, 2012 at 3:40 AM, Robert Haskins robert.hask...@gmail.com wrote: I get a reject, even though the crypt'd passwords match! That's not how crypt works. You don't compare the crypted password. [pap] login attempt with

Re: Problem with crypt passwords matching

2012-08-15 Thread Matthew Newton
On Wed, Aug 15, 2012 at 04:46:09PM -0700, Doug Hardie wrote: [pap] login attempt with password krt444 ... [pap] Using CRYPT password *3u.3LS/VKTOVc I don't know for sure about your system, but most Unix based systems will not generate a * in the encrypted password. Normally that is used