Closed Bug 14520 Opened 25 years ago Closed 7 years ago

jsloader should not expose 'raw' component manager into JS

Categories

(Core :: XPConnect, defect, P3)

x86
Windows NT
defect

Tracking

()

RESOLVED WONTFIX
Future

People

(Reporter: jband_mozilla, Assigned: dbradley)

References

Details

(Keywords: arch, Whiteboard: [PDT-])

in http://bugzilla.mozilla.org/show_bug.cgi?id=13619 we have a plan for a
scheme to build a component manager proxy to be exposed into JS so that security
filtering can be done consistently.

The JSLoader does its own wrapping of the raw component manager and reflects it
into JS as needed to do the NSGetModule call. xpconnect could expose the proxied
component manager and the js loader could use that.

Though we may have no specific security plans for JS components, we should plug
all potential holes and route all calls through safe channels.
Status: NEW → ASSIGNED
Depends on: 13169
Assignee: jband → shaver
Status: ASSIGNED → NEW
Depends on: 13619
No longer depends on: 13169
OK, I'll switch over when the proxy is available, presumably from the XPConnect
service.
Let's try that again, shall we?
Status: NEW → ASSIGNED
Target Milestone: M11
Any news on how I should get the One True Component Manager?  Just a
get-property on the Components object, maybe?

Do we need this for beta?  I'll say ``yes'' for now.
Summary: jsloader should not expose 'raw' component manager into JS → [beta] jsloader should not expose 'raw' component manager into JS
Target Milestone: M11 → M12
say yes or remove beta from the title. -> m12
Summary: [beta] jsloader should not expose 'raw' component manager into JS → [beta] [arch] jsloader should not expose 'raw' component manager into JS
Is there a way to get The One True Component Manager Wrapper yet?
Target Milestone: M12 → M13
There's no good way to get the Component Manager wrapper other than
JS_GetProperty for Components.manager, and our current security policy makes it
currently pointless, so I'm punting to M13 and the completion of the XPConnect
reconstruction.
Setting "no target milestone" to match my dependency (13619).
Moving all XPConnect QA contact to rginda
QA Contact: cbegle → rginda
Due to Beta indication in Summary, putting beta1 into keyword field.
Keywords: beta1
Summary: [beta] [arch] jsloader should not expose 'raw' component manager into JS → [arch] jsloader should not expose 'raw' component manager into JS
Marking pdt-, but we'd like to have it.
Whiteboard: [PDT-]
I'm going to throw this at jband, who I know will throw it back at me as soon as
his part is done.
Assignee: shaver → jband
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Keywords: arch
Summary: [arch] jsloader should not expose 'raw' component manager into JS → jsloader should not expose 'raw' component manager into JS
mass reassign of xpconnect bugs to dbradley@netscape.com
Assignee: jband → dbradley
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Removing Rob as QA contact
QA Contact: rginda → pschwartau
Blocks: 104166
QA Contact: pschwartau → xpconnect
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.