Hello On Sun, 12 Mar 2006 17:47:26 +0100 Peter Bex <[EMAIL PROTECTED]> wrote:
> On Sat, Mar 11, 2006 at 10:58:34PM -0700, Shawn Rutledge wrote: >> Another feature (which might or might not be a good idea) is to have >> folders, rather than a single namespace. A problem arises when you >> try to use a conventional wiki for multiple projects - you have to be >> careful to choose sufficienty verbose titles for the pages, so that >> you don't use up all the good names for one project. So I think I >> will make it possible to partition parts of the wiki in actual >> directories on the server. That way different directories can have >> different permissions too. At work, we used mediawiki for a while, >> and then pretty soon people wanted to have some stuff be public, and >> some be private to our department, and we didn't find a way to do it. >> So we had to make the whole thing private (using a .htaccess file). >> What does Spiffy have for security? > > See the spiffy-access-file parameter. It's a much more flexible and > powerful access mechanism then .htaccess. It allows you to define a > function that determines if one is allowed to view the file or not. > (it returns a boolean, #t if access allowed, #f if denied) > > Maybe people who are more familiar with Apache could contribute some > macros that it easier to specify access in a declarative fashion. > > For course-grained access control, there's the spiffy-deny-access > parameter, which is a regex. Access is denied to any file that matches > the regex. By the way, is anybody using spiffy with some kind of secure authentication or https? Best wishes, Mario _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
