Just fyi,
Yesterday I posted a question on radius 2.0.1 and Linux 2.0.32 We are
running shadow passwords and I do have the shadow.h file.
I had originally compiled radius without the -DNOSHADOW and encountered a
situation where users with the menu would authenticate and users using pap
and chap wouldn't.
Today I recompiled and took out the ifdef options for NOSAHDOW leaving
shadow.h as a standard include file. This is in the radiusd.c file:
#include <syslog.h>
#include <grp.h>
#include <shadow.h>
#include "radius.h"
#include "users.h"
I still got the same results.
Then I went in and took out the calls for PASSCHANGE taking out radpass
support. Honestly I didn't take the time out to figure out what radpass
does.. I am curious..
Anyway I had to leave in the definitions associated with PASSCHANGE in the
radius.h file
/*
#ifdef PASSCHANGE
*/
#define PW_PASSWORD_REQUEST 7
#define PW_PASSWORD_ACK 8
#define PW_PASSWORD_REJECT 9
/*
#endif
*/
/* PASSCHANGE */
Now, everything works. I get both pap and menu logins authenticating.
Just out of curiousity did anyone else have to do this?
I'm also curious on the menu passwords. Why did they get in and the pap
didn't? Is this a potential security problem?
Thanks,
-Rob
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>