308
edits
Security:Security Checks In Glue: Difference between revisions
Jump to navigation
Jump to search
Security:Security Checks In Glue (view source)
Revision as of 22:39, 12 September 2006
, 12 September 2006→Implementation notes
| Line 34: | Line 34: | ||
# Ditch XPConnect for DOM classes. Use glue code, automatically generated as needed, instead. Do some security checks in the glue. | # Ditch XPConnect for DOM classes. Use glue code, automatically generated as needed, instead. Do some security checks in the glue. | ||
# Do the remaining security checks at the very beginning of the DOM methods themselves, but only if the method is the one that's currently being called by the glue (that is, method name and |this| pointer match). This doesn't handle reentry of the method from other parts of the code while it's being called... not sure what we can do about that. This could probably be done without ditching XPConnect, if we used the XPCCallContext stack or something to check what the currently-called method is. | # Do the remaining security checks at the very beginning of the DOM methods themselves, but only if the method is the one that's currently being called by the glue (that is, method name and |this| pointer match). This doesn't handle reentry of the method from other parts of the code while it's being called... not sure what we can do about that. This could probably be done without ditching XPConnect, if we used the XPCCallContext stack or something to check what the currently-called method is. | ||
# Examine all checks that use the subject principal in our current codebase and make sure that equivalent checks are being performed in the new model. | |||