Security Notes on Remote Embedding/ja

Jump to navigation Jump to search
This page is a translated version of the page Security Notes on Remote Embedding and the translation is 5% complete.
Other languages:
English • ‎日本語

You should always be mindful of including remote javascript on your page.

In order to make the player and inline transcripts available we use remote javascript on the page that embeds the content. This makes remote embedding an excellent tool for powerful mash-ups. See how opencongress styles metavid clips embedded in their site.

But with this power comes responsibility. The MediaWiki software and Wikipedia servers take security very seriously. There are two possible compromise situations 1) a bug in the software exposes execution of non-trusted javascript or 2) The hosting server running mediawiki is compromised resulting in execution of non-trusted javascript. Both these problems result in XSS issues for any site that cross embeds the javascript.

You should take into account these security consideration anytime you embed any javascript based widget into your site.

Solution 0: You are already aware of such issues (not a real solution)

You don't have logins on the same server as your content pages,so there are few or no potentially damaging user interactions taking place on your site. Or you still haven't got around to doing a normal xss hole scan on your site,

解決策 1: iframe を使用

This solution won't let you style the transcripts or do any secondary javascript based enhancements. Its also can be awkward in page layout. But essentially you include it with an iframe like so:

 <iframe width="405" height="340"
src="" />

//@@TODO we should probably make iframe the default setting

Solution 2: Copy the mwEmbed library to your server

You can check out a copy of Mv_Embed and use it locally. It will know to remap the video tag and should work fine with the remote content. If you do this you will want to stay current with mv_embed updates that we push out and join the metavid-l developer list. Also you will want to proxy your transcript queries so they are local scrubbed queries instead of javascript injections.