Kristina Pfaff-Harris <[EMAIL PROTECTED]> wrote:
> Question for the developers on the format of a clients.conf entry. (Hm.
> Should we take this discussion of checkrad to the devel list?)
Sure...
> Actually, a few questions, and please, as always, point me to any docs I
> may have missed. First, do the spaces have to be tabs, or can they be any
> kind of space?
There isn't much in the way of docs for the configuration file
format.
The spaces can be tabs or spaces.
> Can you do something like
>
> client 127.0.0.1 { secret = rillyseekrit }
>
> Or do the braces and the config options have to be separated by newlines?
Yes, they do. The parser is *very* dumb.
> Can we have # comments anywhere in the entry, and if so, do comments start
> at the # and go to the end of the line, or does the # have to be at the
> beginning of a line as in "clients"? In other words, can I have this:
>
> secret = rillyseekrit # the secret: shh!
Yes, but only because the parser is broken.
After it reads 'rillyseekrit', it STOPS looking for anything else on
the line. So you can do:
secret = rillyseekrit ignore this stuff
and it will probably parse.
> To read the secret/community string/etc from clients.conf, you'd want
> checkrad to be able to parse every variation of how a user might set up
> that file,
No, I am *severely* opposed to checkrad parsing clients.conf. If
necessary, the server can pass more options to checkrad.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
