Re: Dropping permissions and sandboxing a browser plugin.

As long as you don't do much in the way of responding to web page script
requests, and do very paranoid checking of configuration parameters, then
the vulnerability isn't that great. It's when someone can embed your
plug-in, and then tell it what to do, that you're open for trouble.

Btw: you may want to look into the "instant action" solution. I think it's a
branch of GarageGames, but don't hold that against them -- they may be able
to let you put your current stuff into plug-ins for the major browsers in
pretty fast time.

However, I find that, everytime someone asks me what it would take to "put
something in a browser," what they really want is the following two
features:

1) No download required.
2) Loads as fast as a page of text.

Neither of those will be true when you go the native code in plug-in
approach, mainly because 3D is just so much heavier than 2D or video, and
most people don't understand this difference and why that is. (The solution
is to wait until infrastructure supports fast loading of 3D content, of
course -- that will eventually come)

Sincerely,

jw

--
Americans might object: there is no way we would sacrifice our living
standards for the benefit of people in the rest of the world. Nevertheless,
whether we get there willingly or not, we shall soon have lower consumption
rates, because our present rates are unsustainable.



On Fri, Mar 19, 2010 at 1:28 AM, Boberg, Stefan <[email protected]>wrote:

>    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
>

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