|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: [suse-security] reasonably secure Wiki implementation
From: James Oakley (joakley
solutioninc.com)
Date: Thu Mar 20 2003 - 09:56:44 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 19 March 2003 04:03 pm, Dirk Mueller wrote:
> does anybody have any recommendations for a reasonably secure Wiki
> implementation? I do understand that wiki by design allows editing and
> therefore destroying or manipulation of any page contents, I was more
> looking for a "secure" implementation that makes server compromise rather
> unlikely, and also allows tracking of changes by providing a version
> history and mailing of changes to the administrator for review.
>
> There are many dozen implementations out there.. could anyone who has spent
> some time with looking through them share his experience and
> recommendations with me?
Zope with ZWiki works very well and has multiple undo due to Zope's
transactional db. Zope's access control stuff is extremely good as well.
Making it mail out changes should be fairly simple, too, with a small Python
script.
- --
James Oakley
Engineering - SolutionInc Ltd.
joakley
solutioninc.com
http://www.solutioninc.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+eeS9+FOexA3koIgRAp14AKCOlleCb7gqkJgy/OFyPvKAhVq2IwCfeTM4
GRBGRXU+1Y1idGa52Ys9QeY=
=w8sG
-----END PGP SIGNATURE-----
--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help
suse.com
Security-related bug reports go to security
suse.de, not here
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]