Closed Bug 1233903 Opened 8 years ago Closed 8 years ago

fix up the shumway use of createCodebasePrincipal to be aware of user context origin attributes

Categories

(Firefox Graveyard :: Shumway, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: huseby, Unassigned)

References

Details

(Whiteboard: [shumway][OA])

In shumway's special storage it will need to make sure that it does proper user context isolation by setting the correct user context id in the origin attributes used when calling createCodebasePrincipal.

> browser/extensions/shumway/chrome/SpecialStorage.jsm
>   line 27
>     var principal = ssm.createCodebasePrincipal(uri, {});
IMHO, this is not a blocker fixup for v1 of containers, but it should be considered a blocker for shipping shumway.  Without proper user context isolation, any storage done on behalf of a flash movie won't be properly isolated and shumway could be used as a cross-domain/cross-tab communication channel.
Whiteboard: [shumway]
Chris, are you the PM on shumway?  This bug is a blocker for shipping shumway and I want to make sure the shumway team is tracking it.
Flags: needinfo?(cpeterson)
Thanks. I've updated the Shumway bug dependencies. Shumway will need createCodebasePrincipal bug 1218479, but the Shumway work should not block you.
Blocks: shumway-1.0
No longer blocks: createCodebasePrincipal
Flags: needinfo?(cpeterson)
After fixing up a bunch of other similar cases, I think the right thing to do here is to query the document/docshell for the origin attributes and using that.  Shumway should be isolating based on user context id.
Product: Firefox → Firefox Graveyard
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Why is this resolved incomplete?
Flags: needinfo?(ehumphries)
The github issue is here: https://github.com/mozilla/shumway/issues/2418
Whiteboard: [shumway] → [shumway][OA]
You need to log in before you can comment on or make changes to this bug.