Inn 2.2.1 local newsgroups
Simone Sestini
I need to setup some kind of local newsgroups for one of my customer.
I tested the simple configuration under INN 2.2 but after that i
upgraded to INN 2.2.1 and the feeds won't start anymore.
What i found out is that..
========== CUT HERE ============
Subject: (6.18) Add local newsgroups?
Q: Does anyone have a cookbook example on how to create a local news
group?
These are the steps ..
1) Make sure your innd is running 2) Add the group with: ctlinnd
newgroup local.group 3) Add entries to newsfeeds to restrict the local
groups to your
organization:
ME:!local.*::
out.going.site:*,!local.*:Tf,Wnm:
4) Add a descriptive entry to newsgroups 5) Ready :)
Please consider, that local is a very common name for local groups, so
if a user crossposts to local.test and misc.test the article will show
up in all local.test over the
world. So please choose a 'better' name.
========== CUT HERE ============
So i did this one..
I added the newsgroup swith the ctlinnd command then i went to the
edit the newsfeeds file under the etc dir
MYORGANIZATION:
ME:!local_project.*::
my.news.server.here:*,!local_project.*:Tf,Wnm:
Before all was working great but now with INN 2.2.1 nothing seem to
work correctly.. when i restart the server it go down with that error
over syslog
Sep 27 19:38:28 auth2 innd: SERVER syntax_error
/usr/local/news/etc/newsfeeds
Sep 27 19:38:28 auth2 innd: iunet closed
Sep 27 19:38:28 auth2 innd: ME closed
Sep 27 19:38:28 auth2 innd: mynews.server.here closed
Sep 27 19:38:28 auth2 innd: control:12 closed
Sep 27 19:38:28 auth2 innd: localconn:14 closed
Sep 27 19:38:28 auth2 innd: remconn:4 closed
Someone know how to fix that problem or what i'm doing bad ?
Thanks in advice for any kind of help.
Russ Allbery
> 1) Make sure your innd is running 2) Add the group with: ctlinnd
> newgroup local.group 3) Add entries to newsfeeds to restrict the local
> groups to your
> organization:
> ME:!local.*::
> out.going.site:*,!local.*:Tf,Wnm:
There's an unfortunate formatting error in wherever you found those
instructions. The "organization:" part is part of the preceeding
paragraph and shouldn't be put into newsfeeds.
> MYORGANIZATION:
> ME:!local_project.*::
> my.news.server.here:*,!local_project.*:Tf,Wnm:
Delete the "MYORGANIZATION:" line. That's the syntax error. The other
lines don't have to be indented either, but it probably isn't hurting
anything.
--
Russ Allbery (r...@stanford.edu) <URL:http://www.eyrie.org/~eagle/>
Simone Sestini
Thanks Russ it work..
The other thing i will need to do is to setup some special security on
those kinds of local newsgroups.
For examples. i wanna that only user pippo with password pluto should
have access to the local_project.* newsgroup.
I checked the nnrp.access file and i tried a lot of config but without
any good news..
Any idea ?
Russ Allbery
> The other thing i will need to do is to setup some special security on
> those kinds of local newsgroups.
> For examples. i wanna that only user pippo with password pluto should
> have access to the local_project.* newsgroup.
Something like:
*:RP:pippo:pluto:local_project.*
and make sure you have ,!local_project.* on all other lines in nnrp.access
should do it.
bill davidsen
Russ Allbery <r...@stanford.edu> wrote:
| Simone Sestini <simone....@plugit.net> writes:
|
| > The other thing i will need to do is to setup some special security on
| > those kinds of local newsgroups.
|
| > For examples. i wanna that only user pippo with password pluto should
| > have access to the local_project.* newsgroup.
|
| Something like:
|
| *:RP:pippo:pluto:local_project.*
|
| and make sure you have ,!local_project.* on all other lines in nnrp.access
| should do it.
Is there any documentation on doing this in the new enhanced
inn-2.[23] with readers.conf? I think this stuff rots beyond belief for
any site which has a lot of by-IP and by-password validation in 2.0.
I'm still running a couple of old servers bacause of this, until I
retrofit the working code back into 2.3 or find a way of doing this with
readers.conf which doesn't take 3 sec/connect of CPU time.
--
bill davidsen <davi...@tmr.com> CTO, TMR Associates, Inc
When taking small children to a carnival, always have them go potty
*before* you let them go on the rides, and let them eat all the junk
food and candy *after*.
Marius Kaizerman
> > have access to the local_project.* newsgroup.
>
> Something like:
>
> *:RP:pippo:pluto:local_project.*
>
> and make sure you have ,!local_project.* on all other lines in nnrp.access
> should do it.
This is not working as expected. For example,
I want that any user from any host can access the
whole groups without a username and password
except the local.food group. I'm using inn-2.2-8
on RH6 and my nnrp.access file includes the following lines:
*:RP:::*,!local.food
*:RP:user:passwd:local.food
The result is that inn asks for a password for ANY group
accessed, and not only the local.food one, untill I'm
removing the 2nd line.
Marius.
Marius Kaizerman
> > This is not working as expected. For example, I want that any user from
> > any host can access the whole groups without a username and password
> > except the local.food group. I'm using inn-2.2-8 on RH6 and my
> > nnrp.access file includes the following lines:
>
> > *:RP:::*,!local.food
> > *:RP:user:passwd:local.food
>
> > The result is that inn asks for a password for ANY group accessed, and
> > not only the local.food one, untill I'm removing the 2nd line.
> You have two entries matching *, so only the second one will ever be used.
>
> Unfortunately, it's very difficult (maybe impossible) to do what you're
> trying to do using nnrp.access alone. I think it's possible with the Perl
> authentication hooks, and it should be possible using readers.conf.
Thanks.
I'm using inn 2.2-8. Which version uses the readers.conf ?
Marius.
bill davidsen
Marius Kaizerman <mar...@actcom.co.il> wrote:
| Thanks.
| I'm using inn 2.2-8. Which version uses the readers.conf ?
That's part of 2.3. You can do what you want, one auth stanza and two
access stanzas, I believe.
Marius Kaizerman
> | I'm using inn 2.2-8. Which version uses the readers.conf ?
>
> That's part of 2.3. You can do what you want, one auth stanza and two
> access stanzas, I believe.
When it's going to be released ?
Marius.