problem with readers.conf
Javi Pardo
dakota at dakotabcn.net
Sun Nov 18 23:27:53 UTC 2007
Hello Jeffrey!
> On Sun, 18 Nov 2007, Javi Pardo wrote:
>
>
>> Groups publics without Password with Read Write permissions
>> Private Group "A" with 20-30 users
>> Private Group "B" with 10 users
>>
>
> Okay!
>
> It's understandable that you're having trouble; you've found an area where
> readers.conf is not as powerful as we might want.
>
> We have three options to keep track of what user has what level of access:
>
> (1) Change usernames to include domains with that information, such
> as "javi at publico.dakotabcn.net" instead of just "javi". This is
> easy on the server, but means that you have to get your users to
> reconfigure their clients. It also means exposing some internal
> information to your users, which may or may not matter. If your
> usernames are already in this format
>
Ok, i probre first this solutions i changed the readers.conf and in this
moment are with this config:
## $Id: readers.conf 4371 2001-01-16 15:35:38Z rra $
auth "localhost" {
hosts: "localhost, 127.0.0.1, stdin"
default: "<localhost>"
}
auth PublicoAccess {
# hosts: "*"
auth: "/usr/bin/ckpass.py -f /injail/inn/etc/accesos/publicos.cfg"
default-domain: publico.dom
}
auth Privados {
auth: "/usr/bin/ckpass.py -f /injail/inn/etc/accesos/privados.cfg"
default-domain: privados.dom
}
auth AllWorldRead {
hosts: "*,!10.35.228.224/27"
# default-domain: publico.dakotabcn.net
}
access "localhost" {
users: "<localhost>"
newsgroups: "dakota.*"
access: RPA
}
access PublicoAccess {
# users: "*"
users: *@publico.dom
newsgroups: "dakota.*,!dakota.privados.*"
}
access Privados {
users: *@privados.dom
read: "dakota.privados.*"
post: "dakota.privados.*"
}
access "AllWorldRead" {
read: "dakota.*,!dakota.privados.*"
post: "dakota.escritura,!dakota.privados.*"
}
with this config this the result i have delete the redlocal.
localhost: WORKS, no problem
AllWordRead is the access without password: not work, the access no
returns groups, if connect with telnet returns 480 Authentication
required for command, why?
Privados: works! the use is without @privados.dom, if use
javi at privados.dom not work
publicoaccess: not work...
because not work?
regards
> (2) Leave the usernames the same, but hardcode this list of who has
> which access into readers.conf. This is fairly straightforward
> to set up for a small number of users but can be painful if you
> have frequent changes (because information has to be maintained
> in two places, the password file and readers.conf).
>
> (3) Use a custom script to get exactly the behavior you want. (One
> way to do this would be to use the script samples/nnrpd_access.pl
> that lets you continue using nnrp.access. This is suboptimal
> but worth considering.)
>
>
> Any idea which of these you'd like to try?
>
>
>
More information about the inn-workers
mailing list