On Tue, Jan 11, 2011 at 3:33 PM, Joshua Tacoma <email@example.com>
> > - Are the security issues so obviously and deeply hairy that no one in theirThanks, I was wondering about that... some ways to fix this:
> > right mind would do such a thing?
> has access to the cookie (and thus the session) of the user who is
> browsing the page, and can act in that user's name on the wiki, doing
> anything the user can do.
- Enable the formatter only on certain pages (is this possible?), keep
restrictive ACLs on those pages, and make sure visitors and
contributors are informed about the risks of using the site.
- Enable the formatter only for localhost clients, and setup a
read-only proxy on the same machine that is accessed through a
distinct domain name, so that normal protections against cross-site
scripting block access to the wiki.
- Only generate JSON (from tables or yaml snippets) and maybe invent a
simple DSL or two that could be translated to reliably safe