Confirmed users, Bureaucrats and Sysops emeriti
419
edits
XPConnect:Security:XPCNativeWrapper Automation: Difference between revisions
XPConnect:Security:XPCNativeWrapper Automation (view source)
Revision as of 22:07, 17 May 2005
, 17 May 2005→Notes on the new XPConnect security model
| Line 26: | Line 26: | ||
** allow app and extension files to opt into XPCNativeWrapper automation | ** allow app and extension files to opt into XPCNativeWrapper automation | ||
** this means a wrapper-sharing policy declaration in the chrome manifest | ** this means a wrapper-sharing policy declaration in the chrome manifest | ||
* | * Resolved issues | ||
** should "system" applied to a script mean has system principals, or wants system XPCNativeWrapper? | ** should "system" applied to a script mean has system principals, or wants system XPCNativeWrapper? | ||
** if so, we have enough bits, and HasSystemPrincipal checks can be optimized | ** if so, we have enough bits, and HasSystemPrincipal checks can be optimized | ||
| Line 32: | Line 32: | ||
*** JS_FlagScriptFilenamePrefix can take a flags argument | *** JS_FlagScriptFilenamePrefix can take a flags argument | ||
*** do we want JS_UnflagScriptFilenamePrefix? do we ever unload chrome? | *** do we want JS_UnflagScriptFilenamePrefix? do we ever unload chrome? | ||
** the resolution: | |||
*** bsmedberg will support an xpcnativewrappers=yes option in the chrome manifest | |||
*** this will cause chrome to get the XPConnect service and call its new wantXPCNativeWrappers(filenamePrefix) method | |||
*** which will call JS_FlagScriptFilenamePrefix | |||