problem with readers.conf

[Jeffrey M. Vinocur]

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 

  (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?  


-- 
Jeffrey M. Vinocur
jeff at litech.org