2010/1/6 Søren Gjesse <[email protected]> > I have nothing to add to the accurate answers Yury provided, but Yury can > you provide some details on the security related problems you are working on > solving? > > The problems are connected with the utility context we use for DOM inspection. It has access to all the inspected contexts which may lead to object leaks between contexts that were isolated before the inspection(e.g. contexts of iframes from different domains that can't access each other). The solution is to get rid of the utility context with universal access and have some inspector code compiled directly in each of the inspected contexts. The code is executed in the scope of the context where it has been compiled. There might be similar issues with v8 debugger since it has one debugger context that has access to all the debugee contexts. Though, it might no be a problem given that all the objects inspection is done by means of calls to runtime.cc and no user code is executed in the debugger context and as such can't get access to the objects from the debugger context.
Yury
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
