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

security: start removing the possible use of frames. #538

Merged

Conversation

monkeyiq
Copy link
Contributor

@monkeyiq monkeyiq commented May 6, 2019

There is only one area that I can see that uses frames/iframe in filesender. This is to support legacy browsers that do not support the FileReader API. The FileReader is supported on IE10 and many older browsers (https://developer.mozilla.org/en-US/docs/Web/API/FileReader#Browser_compatibility). This makes the legacy iframe code very unlikely to be useful these days.

As such I have made the default policy for X-Frame-Options to be deny. The iframe code has not been pruned yet in case it is discovered to be required by some sites and the X-Frame-Options can be adjusted to allow it again. If nobody notices that x-frame is denied then the legacy code can be pruned away.

@madsi1m
Copy link
Contributor

madsi1m commented May 6, 2019

Will this break filesender if i run filesender it self in an iframe?

@monkeyiq
Copy link
Contributor Author

monkeyiq commented May 6, 2019

Ah, good point. Will sameorigin work for you there?

@madsi1m
Copy link
Contributor

madsi1m commented May 6, 2019

Should do, can test once it is merged

@monkeyiq monkeyiq merged commit f3da6e3 into filesender:master May 6, 2019
@monkeyiq
Copy link
Contributor Author

monkeyiq commented May 6, 2019

If it doesn't work I'll revert later in the day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants