This repository was archived by the owner on Feb 16, 2021. It is now read-only.
IFrame security analysis pages #17
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created test pages to analyze iframe sandboxing and its impact on ZeroClipboard (a sandboxed
iframe
is not allowed to instantiate plugins).This is why ZeroClipboard no longer works on JSFiddle, CodePen, etc. However, the analysis results illuminated at least one interesting possibility: both of those sites have their sandboxes setup such that they could be removed by the child frame and readded afterward (if readding it doesn't destroy plugin instances, that is). So, we can at least show those who want to use ZeroClipboard on JSFiddle/CodePen how to game the system and explain to them why it is necessary (boo, Flash Player).
Ref zeroclipboard/zeroclipboard#511
http://zeroclipboard.org/test-iframes.html (or locally, http://localhost:3000/test-iframes-local.html)