Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider making RTCCertificate throw when serialized when _forStorage_ is false #2257

Closed
annevk opened this issue Aug 6, 2019 · 3 comments

Comments

@annevk
Copy link
Member

commented Aug 6, 2019

This would make postMessage() and friends throw and only allow same-origin usage of the object as seems to be intended. This would allow you to get rid of the [[Origin]] field and prevent inadvertent sharing of this object with untrusted origins (who might be able to Spectre-attack its contents at that point, unless the user agent has a more convoluted design whereby it only messages a pointer around and keeps the actual underlying data only in processes accessible to the origin that created it).

@annevk annevk changed the title Considering making RTCCertificate throw when serialized when _forStorage_ is false Consider making RTCCertificate throw when serialized when _forStorage_ is false Aug 6, 2019
@alvestrand alvestrand added this to To do in WebRTC 1.0 to PR Aug 22, 2019
@jan-ivar jan-ivar added PR exists and removed Ready for PR labels Sep 11, 2019
@aboba aboba added the TPAC 2019 label Sep 12, 2019
@dontcallmedom

This comment has been minimized.

Copy link
Member

commented Sep 25, 2019

TPAC discussion points toward keeping the capability to use postMessage, maybe limiting it to same-origin communication and calling attention to security risks.

@jan-ivar

This comment has been minimized.

Copy link
Contributor

commented Sep 26, 2019

@annevk Anything else we can do here to somehow limit postMessage use to same origin?

@annevk

This comment has been minimized.

Copy link
Member Author

commented Sep 26, 2019

I have an idea for a design inspired by you at whatwg/html#4939. I'd like to know if others are somewhat okay with it before writing the text though. I can file a new issue once that's in place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
4 participants
You can’t perform that action at this time.