group access control
Brought to you by:
m-a
Menu
▾
▴
#2 group access control
If I create some local groups and give my friends
access to them, then (as far as I can tell) there is
no way to stop them from reading any other newsgroup
on USENET, thus possibly clogging up my hard-drive.
It would be useful to have some way to control the
output of a LIST NNTP command so that I can restrict
access to groups depending on who is connected.
Perhaps have a NNTP_LIST environment variable that
gives the name of a file containing a glob style
list of newsgroups to be given at a LIST command.
I could then control access through hosts.allow
as with the NOPOSTING env. var.
Logged In: YES
user_id=48167
I just read the RFC and want to modify this a bit:
* Have an environment variable of LEAFNODE_GROUPS that
contains a list of newsgroups of the same form as with the
NEWNEWS command. This should be easy for leafnode to translate.
* Perhaps generate a temporary groupinfo file?
Superficially this sounds like it might be easier to use an
alternative groupinfo file, but I know nothing of the
internals of leafnode. Would the real groupinfo file have
to be updated after operations, or do texpire and fetchnews
handle this?
* LIST, NEWGROUPS, NEWNEWS and GROUP need to give
non-default responses (and perhaps POST). If you generate a
temporary groupinfo file then I suppose this would be taken
care of automatically.