Re: Portmaster RADIUS Users Digest V95 #5

Radius Administrator (radius@goofy.zdv.Uni-Mainz.de)
Thu, 28 Sep 1995 12:20:47 +0100

>
>From: Garry Shtern <shterng@buster.law.nyu.edu>
>Date: Wed, 27 Sep 1995 17:14:10 +1030 (???)
>Subject: Re: Problems with Radius 2.4
>
>>
>> You only take out -DNOSHADOW if you _have_ /usr/include/shadow.h and
>> you probably don't have it, so you should leave NOSHADOW defined.
>
>Well I have /usr/include/shadow.h, because I run shadow passwords on my
>system.. and it still gives me that message... if you have any ideas I
>would really appreciate them...
>

If you want to compile something with Shadow-Pwd support under Linux
you must:

a) Install the shadow libraries (either John F. Haugh's shadow-suite
or the NYS switching library)

b) Add -DSHADOW_PWD (or is it -DSHADOW ?) to CFLAGS (for JFH's shadow
suite) or change the configuration for passwd lookups in
/etc/nsswitch.conf (for NYS library)

BTW: <shadow.h> has always been there, because the libc has always
had the stubs. But until recently there has been no GPL'ed shadow
library. That has changed with NYS which is now a part of libc (since
libc-5.0.0, which is also in ELF not a.out format)

>>
>> > also it keeps on telling me that _BSD_SOURCE is redifined....
>>
>> This is a problem with the Linux distribution, as far as I can tell.
>> Two include files define the _BSD_SOURCE macro, but not identically.
>> Then to make matters worse, the one file includes the other...
>

Yeah. I was always convinced that the linux libc headers are really
messed up.

>
>Is there anything you would recomend.. Like going into the include files
>and changing them manually.. Or would I just be better off not touching
>them at all?
>

Leave them alone unless you know _EXACTLY_ what you are doing!

Cheers,
Dominik Kubla,

---
Johannes Gutenberg-Universität       Phone: +49 6131 39-3353
Zentrum für Datenverarbeitung        Fax  : +49 6131 39-6407
Anselm-Franz-von-Bentzel-Weg 12      eMail: kubla@Uni-Mainz.DE
D-55099 Mainz, Germany