Closed
Bug 1034239
Opened 11 years ago
Closed 11 years ago
Switch the current GentlyOpaque security wrapper to an Opaque XrayTrait
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
FIXED
mozilla33
People
(Reporter: bholley, Assigned: bholley)
References
Details
Attachments
(2 files)
1.79 KB,
patch
|
gkrizsanits
:
review+
|
Details | Diff | Splinter Review |
19.22 KB,
patch
|
gkrizsanits
:
review+
|
Details | Diff | Splinter Review |
I did this wrong before. Making this a SecurityWrapper means that the caller does not subsumes the target, and that the target therefore needs to be protected from the caller. But GentlyOpaque was supposed to be an analog of PermissiveXray for use when no useful XrayTraits exist, so it should behave similarly.
If we make this a Filtering Security Wrapper, we get a bunch of assertions where we expect CheckedUnwrap to succeed for a chrome-side wrapper. And we can't making it a Filtering Non-Security Wrapper, because then the filtering policy isn't even consulted (an optimization in jsproxy.cpp).
Really, we want all of the Xray machinery (like the ability to waive and to place expandos), and we just don't want to resolve any properties. This patches in this bug will do that.
Assignee | ||
Comment 1•11 years ago
|
||
Assignee | ||
Comment 2•11 years ago
|
||
Attachment #8451087 -
Flags: review?(gkrizsanits)
Assignee | ||
Comment 3•11 years ago
|
||
I did this wrong before. Making this a SecurityWrapper means that the caller does
not subsumes the target, and that the target therefore needs to be protected
from the caller. But GentlyOpaque was supposed to be an analog of PermissiveXray
for use when no useful XrayTraits exist, so it should behave similarly.
If we make this a Filtering Security Wrapper, we get a bunch of assertions where we
expect CheckedUnwrap to succeed for a chrome-side wrapper. And we can't making it
a Filtering Non-Security Wrapper, because then the filtering policy isn't even
consulted (an optimization in jsproxy.cpp).
Really, we want all of the Xray machinery (like the ability to waive and to place
expandos), and we just don't want to resolve any properties. This patch does this.
Assignee | ||
Updated•11 years ago
|
Attachment #8451088 -
Flags: review?(gkrizsanits)
Updated•11 years ago
|
Attachment #8451088 -
Flags: review?(gkrizsanits) → review+
Updated•11 years ago
|
Attachment #8451087 -
Flags: review?(gkrizsanits) → review+
Assignee | ||
Comment 4•11 years ago
|
||
Comment 5•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/31ac9fc7c668
https://hg.mozilla.org/mozilla-central/rev/fd0234ab4582
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla33
You need to log in
before you can comment on or make changes to this bug.
Description
•