Closed Bug 524994 Opened 11 years ago Closed 11 years ago
Flatten out wrapper hierarchy
Currently, we purposely do things like creating SOWs around SJOWs in order to enforce security properties. This works, but is overly complicated. We should, instead, be able to tell the SJOWs to enforce SOW-like security properties.
Blocking 1.9.2 as this is required to fix blocker bug 520522.
Priority: -- → P2
Target Milestone: --- → mozilla1.9.2
Bug 520522 is no longer a blocker, and thus neither is this.
Flags: blocking1.9.2+ → blocking1.9.2-
Comment on attachment 423098 [details] [diff] [review] refreshed - In EnsureLegalActivity(): // Otherwise, we're looking at a non-system file with a handle on an // implicit wrapper. This is a bug! Deny access. - return ThrowException(NS_ERROR_XPC_SECURITY_MANAGER_VETO, cx); + NS_ERROR("Implicit native wrapper in content code"); +#else + return JS_TRUE; +#endif + + // NB: Watch for early returns in the ifdef DEBUG code above. } Does the above not leave us not returning a value at all in debug code? r=jst with that fixed.
Attachment #423098 - Flags: review?(jst) → review+
Blake: any progress on getting this fixed on trunk and branch patches together for 184.108.40.206 and 220.127.116.11
mrbkap: please see comment 6?
blocking1.9.1: .9+ → needed
Flags: blocking18.104.22.168+ → blocking22.214.171.124-
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.