Boris Zbarsky wrote:
> Not for purposes of automated XPCNativeWrapper, because the extension
> system is completely different.  See 
> <http://users.skynet.be/fa258499/hackexttutorial.html#note4>

Thanks for this information. So far I've thought that I'm secured by the 
automatic XPCNativeWrappers...

> It can be made dangerous with a bit of effort on the part of the page.

I tried several things. For example function.stack isn't accessible by 
the page code. Maybe it's a bit difficult to do bad things, but if it's 
not impossible, then PrefBar currently has a security hole if installed 
on SM 1.1.x...

> I think you can just set chrome:xpcNativeWrappers="yes" on your
> RDF:Description in your contents.rdf...

It seems to be chrome:xpcNativeWrappers="true"

http://lxr.mozilla.org/seamonkey/search?string=chrome%3Axpcnativewrappers

Tried that and it seems to work fine.

> There is, as it happens, in the case (not recommended) that you decide
> to not use automatic XPCNativeWrappers.  I thought I'd documented it
> pretty thoroughly at 
> http://developer.mozilla.org/en/docs/XPCNativeWrapper#Deep_vs._Shallow and 
> http://developer.mozilla.org/en/docs/XPCNativeWrapper#XPCNativeWrapper_constructor_call_with_no_string_arguments
>  
> 

I definetly want the automatic wrappers. I just didn't know so far that 
I have to enable them by myself. May I trust the automatic wrappers or 
should I still create a wrapper manually where I access untrusted 
content?

> but I would welcome feedback on making the documentation clearer....

In my opinion a short note about

chrome:xpcNativeWrappers="true"

in SeaMonkey 1.1.x is required! Maybe just one or two sentences. It was 
pretty difficult to find that out and if you didn't tell me, I probably 
would still think I'm secured by the automatic wrappers. It's IMHO 
dangerous if developers think that SeaMonkey could work like FF 1.5 and 
so don't add the required switch to contents.rdf...

CU

Manuel

_______________________________________________
dev-security mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security

Reply via email to