Ticket #4051 (closed enhancement: fixed)
Provide a more secure (from spammers mostly) default trac setup
| Reported by: | Jorge <jorge.vargas@…> | Owned by: | jonas |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.10.5 |
| Component: | general | Version: | 0.10 |
| Severity: | major | Keywords: | permission |
| Cc: | jorge.vargas@… |
Description
Hello
As far the initial setup is concern a new trac install gives full write access to anyone, this is a good setup if we live in a good world, but in a world where spammers ruin open source it's a big problem.
I know that trac admins should set this right but the sad truth is that not everyone does it, and we end up with sad things like http://deliciouspython.python-hosting.com/report/1 and http://deliciouspython.python-hosting.com/timeline
so how about some more safe default features?
as a more advance setup here is what we want to use at Turbogears trac. please note we are not using the wiki component, for that I suggest create/delete for level 3 and modify for level 2
1- anon 2- user 3- developer 4- administrator 5- root
each group will inherit the permissions of the above.
permissions from http://trac.edgewall.org/wiki/TracPermissions
1- *_VIEW, except REPORT_SQL_VIEW and probably CONFIG_VIEW 2- TICKET_CREATE,TICKET_APPEND 3- - REPORT_SQL_VIEW - REPORT_CREATE,REPORT_MODIFY (this may be usefull when your working on a feature, but should be abused.) - WIKI_MODIFY (so he/she can delete the page, and put a sign pointing to docs.turbogears.org) 4- - TICKET_ADMIN - REPORT_ADMIN 5- - MILESTONE_ADMIN - WIKI_ADMIN


