Last modified 16 years ago
Last modified on 12/05/08 15:42:00
Analysis
Overview
This task should provide the availability of the server. You have to revise the security of the wiki.
Task requirements
- restarting the server should not affect its availability
- you should fix the registering of users and their permissions
- you should look on Trac session and if they do not end you should fix this
Task result
more stable and secure wiki
Implementation idea
Use TracGuide.
Related
SCS_WIKI_MAINTENANCE_R1
SCS_WIKI_SETUP_R0
How to demo
- Restart the server and show that it is still available.
- show to the team how to register and the permissions the new user has.
Design
Currently the server is set up to boot on power up. Trac is present in start-up scripts automatically so no changes are needed. Research
- Account Manager Plugin http://trac-hacks.org/changeset/3799
- ReCapcha. See http://recaptcha.net/ and see license, include it if possible. Find out what the problem with registering new users is.
- Setup an smtp server to handle the e-mail verification.
- Search for Account Manager Plugin and reCapcha in http://trac-hacks.org
Setup
- Setup the account manager with following requirements:
- Anonymous users can only read
- Registered users can post comments and new tickets
- More permissions if are wanted should be requested by an e-mail.
- Registration should require an e-mail verification.
- Anti-bot protection should be present
Search for session timeout. (not possible for now http://trac.edgewall.org/ticket/2333)
Implementation
- Another Trac environment is set to a better server. The address is http://62.44.108.3/projects/ for now, since it is in testing.
- It has working Account Manager Plugin with regitration module and ReCapcha plugin for Anti-bot protection.
- It runs as an apache module and uses PostgreSQL instead of SQLite3.
- The blog, forum and ticket system are successfully migrated, but there is a slight problem with the wiki pages and the environment is not ready to be useed yet.
Testing
Comments
Log
