OK, I see. Well of course you do have a few solutions, not all being cost
effective. The easiest would be to either setup static IP accounts, or
packet filters, this is also the cheapest.
You are limited by using dynamic IP assignments. We have static only IP
assignments at my organization, mostly for security purposes and purposes
related to things like this with different levels of access/authentification.
You could setup another news server that is more adult-oriented and have
a password only given to your adult users, but this is more cost prohibitive.
My recommendation is to bite the bullet, read the manuals and figure out
the packet filters. Its the only way.
DB
> > Why would you want to put a password on just the READ aspect? If you allow
> > access via password authentification, then you would allow READ and possibly
> > WRITE, not just WRITE.... that makes no sense.
> >
> > You can allow/deny access via IP address, and then you can allow/deny access
> > via password authentification. This should be more than enough security.
> > I have not had one instance of someone reading my newsgroups that I have not
> > wanted to, especially accounts with packet filters from the PM2E...
>
> Technical Support - Applied InterNet Solutions
>
> - Jeremy T. Elston - System Engineer
> (TechSupport@ais.ais-gwd.com)
>