Skip to Content.
Sympa Menu

en - Re: [sympa-users] Restricting list configuration access, even to list owners

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Olivier Salaün - CRU <address@concealed>
  • To: Dale Ghent <address@concealed>
  • Cc: address@concealed
  • Subject: Re: [sympa-users] Restricting list configuration access, even to list owners
  • Date: Tue, 07 Feb 2006 11:28:09 +0100

Hello Dale,

Sympa provides an easy way to hide some list parameters and provide only read-access to others.
This can be configured via the edit_list.conf file, a default one being distributed with Sympa. Below is a sample edit_list.conf :
user_data_source                owner,privileged_owner          hidden

include_file                    owner,privileged_owner          hidden

include_remote_file             owner,privileged_owner          hidden

include_list                    owner,privileged_owner          hidden

include_sql_query               owner,privileged_owner          hidden
[...]
default                         privileged_owner                write
default                         owner                           write
default                         editor                          read
default                         listmaster                      write

Here is the related documentation : http://www.sympa.org/doc/html/

Dale Ghent wrote: Later this spring, I'm going deploy Sympa as a replacement to our  current ListProc server of 2100 lists here at UMBC.

I love the LDAP data sources, as making automatically maintained  campus wide lists based on affiliation (student, staff, faculty, etc)  really eases a large burden on us, but I have a concern about the  implications this configurability has vis a vis list owners who  shouldn't be toying with it.

Is it possible to make certain Data Sources configuration areas for a  given list to be viewable and configurable by only the site-wide  listmasters, denying even the owner of the list the ability to view  or manage the data source in question?

My reasoning is that I don't want to configure, say, a all-students  list for someone using the LDAP data source, and the owner, who may  own other lists, getting a big idea and copying that  data source  configuration to other lists (or giving that info to other list  owners who may then use it) and before I know it, people have  conveniently made their own all-students lists without my knowledge.




Archive powered by MHonArc 2.6.19+.

Top of Page