On 11 January 2011 15:41, Radomir Dopieralski <moinm...@sheep.art.pl> wrote: > On Tue, Jan 11, 2011 at 9:36 PM, Joshua Tacoma <joshua.tac...@gmail.com> > wrote: > > - Are the security issues so obviously and deeply hairy that no one in their > > right mind would do such a thing? > Yes, there are security issues. Basically, the javascript on the page > 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.
Thanks, I was wondering about that... some ways to fix this: - 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 javascript, for operations over the JSON data. ...what do you think? -- Josh ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Moin-user mailing list Moin-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/moin-user
