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.

Sign up for GitHub

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

Jump to bottom

Security quagmire #1

Open

dontcallmedom opened this issue Jan 29, 2015 · 0 comments

Contributor

dontcallmedom commented Jan 29, 2015

There are several ways a media element's content may become unreadable to other APIs:

EME: although the spec is pretty handwavy about it, it suggests that protected content be handled as if there was no media at all
cross-origin sources: content sourced from a different origin (without CORS) triggers a SecurityError (I think)
webrtc can produce "isolated" MediaStreams which once put in a media element behaves like a cross-origin media source

There may be more (?), but in any case, that's one aspect where coordination and cross-API verification would help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment