hurst <
[email protected]> writes:
Also in some examples of readers.conf what is the key option? how is it different from using the same name for the default identity and access
name?
key is primarily useful when you want to support more than one
authentication system at the same time and their identity spaces may
overlap. So you need to distinguish from, say, the Kerberos identity
eagle and the PAM identity eagle and map them to different access rules.
In other words, you probably don't need to use it. It's for fairly
complicated authentication setups.
Also I think as a personal choice you should be able to use the old nnrpd.access file or readers.conf not be forsed to use only one.
readers.conf was in retrospect rather too complicated in its typical configurations, but it's hard to support more than one configuration
system that does the same thing (particularly given how limited the
resources for doing INN development are).
That said, there is a script in contrib called nnrp.access2readers.conf
and in theory you can write the nnrp.access file and then run that script
on it and use the resulting readers.conf, and just repeat that process
whenever you want to change something. (It doesn't support 100% of the
syntax, though.)
--
Russ Allbery (
[email protected]) <
https://www.eyrie.org/~eagle/>
Please post questions rather than mailing me directly.
<
https://www.eyrie.org/~eagle/faqs/questions.html> explains why.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)