nnrp conf
Julien ÉLIE
julien at trigofacile.com
Tue Dec 2 16:35:38 UTC 2014
Hi Edwardo,
> in the virtual brewery example, we will allow any NNTP client in the
> Virtual Brewery domain to both read and post to al$
>
> # Any host with the Virtual Brewery domain may Read and Post to all
> # newsgroups
> *.vbrew.com:RP::*
It is the first example in the readers.conf documentation:
Probably the simplest useful example of a complete readers.conf,
this gives permissions to read and post to all groups to any
connections
from the "example.com" domain, and no privileges for anyone
connecting
elsewhere:
auth example.com {
hosts: "*.example.com, example.com"
default: <LOCAL>
}
access full {
newsgroups: *
}
> # Virtual Brewery - nnrp.access
> # We will allow public reading of all newsgroups except our private
> one.
> *:R:::*,!rec.crafts.brewing.private
And this one is the second example in our documentation:
If you have some systems that should only have read-only access to
the server, you can modify the example above slightly by adding an
additional auth and access group:
auth lab {
hosts: "*.lab.example.com"
default: <LAB>
}
access lab {
users: <LAB>
read: *
}
> this methods so easy a child cant get it wrong why for love of god was
> changed?
I do not understand well how you would have wanted the examples provided
with INN to be more clearer than that.
You just have to use "*.vbrew.com" instead of "*.example.com" and
"*,!rec.crafts.brewing.private" instead of "*". It is exactly what
you already wrote in nnrp.access!
> and my boss not threaten fire me like now
> for letting competition ISP customer use our server.
Well, you just had to use the first two examples shipped in the
readers.conf
documentation...
http://www.eyrie.org/~eagle/software/inn/docs/readers.conf.html#S5
In case you have another needs that are not covered in the examples,
do not hesitate to tell and I will be happy to add them to the
documentation.
--
Julien ÉLIE
More information about the inn-workers
mailing list