Re: Dropping permissions and sandboxing a browser plugin.

    I think the only browser which does this to a large extent is Google Chrome. They have *a lot* of infrastructure set up to sandbox each tab - sandboxing native code properly is really quite difficult. AFAIK, all other browsers rely on the plugin itself (or the .NET runtime) to do their own sandboxing internally.

/Stefan

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Juan Linietsky
Sent: 19 March 2010 00:01
To: [email protected]
Subject: [Sweng-Gamedev] Dropping permissions and sandboxing a browser plugin.

Hi! I've been requested to write an existing game as a web plugin..
I've been researching into this and, while writting a plugin seems to be very straightforward, i'm very worried about the security issues, potential vulnerabilities, etc.
How do existing web plugin engines such as Unity handle this threat to avoid exploits? (if they do at all?)

So far, If i got it right, it seems as the proper thing to do is to drop process permissions to minimize the risk, but i can't really find a lot of information/documentation about sandboxing or any third party library that one can use or licence in order to do this. Information on this would be very appreciated!

Juan Linietsky
_______________________________________________
Sweng-Gamedev mailing list
[email protected]
http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com

_______________________________________________
Sweng-Gamedev mailing list
[email protected]
http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com