I'm developing a wiki for which security is a concern, and I'm trying to figure out which packages would work for what we need it to do. If the package has ACL, is there a need for host blocking? The plan is to have people register to edit and have a user agreement that spells out the guidelines when they register. If they cause trouble, as I understand ACL, I can take them off the user list so they can't edit. But would there be a need w/a persistent vandal to possibly host block?
Offline
I've posted this at one other place, so sorry for unintentional duplication, but:
eTouch SamePage offers very granular security control. Security can be implemented at both the project and page level. Members of a project have full Read/Edit/Comment access, but page owners can restrict these rights for certain pages within projects if they choose to.
The security umbrella even extends to search results: therefore one cannot see search results for a keyword for a page that is inaccesible to you.
Hope that helps
Offline
Even without ACLs, in almost any wiki you can restrict access on the authenticiation level. If a user breaches the user agreement you can simply disable the user account, thus prevent a login by the user...
See related topic on fighting spam at http://www.wikimatrix.org/forum/viewtopic.php?id=244
-- Peter AT StructuredWikis DOT com - http://www.structuredwikis.com/ - http://twiki.org/
Offline
You are not logged in.