On Thu, Sep 02, 1999 at 10:43:24AM +1000, Hugh Irvine wrote:
> > My idea is that if a user is a member of the unix group "email", then
> > they are authenticated by the first DEFAULT paragraph, and get a filter
> > which restricts them to email only. If not, then they get the paragraph,
> > and have no filters set for them. This makes it very easy for us to
> > manage our users, simply by making them members (or not) or certain
> > groups. However, I now have a problem: If a user has the primary group
> > "email", radiator does not use it, and auths them with the second entry.
> > However, if I now put the username into the /etc/group file with group
> > "email", it works OK. This becomes a problem because I have more than
> > 1000 users, and the entries in the /etc/group file are limited to a
> > certain length. Is this a failing in Radiator, or am I doing something
> > wrong?
>
> You aren't doing anything wrong - Section 13.1 of the Radiator 2.14.1 reference
> manual explicitly states that the Group check item will check the UNIX
> /etc/group file. I think you will have to do something different - possibly
> have two separate users files corresponding to your two groups.
I found the problem. I am using 2.13.1 and there was a bug in it. from
the changelog:
"AuthBy SYSTEM now checks the primary group as well as the secondary
groups. It used only to do the secondaries."
I think I need to get the updated version.
--
See complete headers for more info
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
