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

CSP, Content Security Policy #743

Open
itst opened this issue Dec 11, 2020 · 2 comments
Open

CSP, Content Security Policy #743

itst opened this issue Dec 11, 2020 · 2 comments

Comments

@itst
Copy link

itst commented Dec 11, 2020

I am struggling to make the webplayer work on a site using CSP.

The issue seems to be that Podlove, once loaded from the whitelisted cdn.podlove.org location, and using a nonce'd episode config, sets out to create additional script, style, and iframe tags. The ifames contain additional script and style tags.

Console looks like this: https://imgur.com/T3m8khq

Before I get into an argument to 'unsafe-inline' everything, is CSP support anywhere on your roadmap?

@alexander-heimbuch alexander-heimbuch transferred this issue from podlove/podlove-web-player Dec 11, 2020
@alexander-heimbuch
Copy link
Contributor

alexander-heimbuch commented Dec 11, 2020

Hey Sascha,
a lot of elements are created in a dynamic manner. Especially creating the sandboxing iframe without a src is a potential issue for CSP. So I guess there won't be any other way than unsafe-inline. If you know a compliant solution I would appreciate any help.

@itst
Copy link
Author

itst commented Dec 11, 2020

I don‘t know about source-less iframes - could that work via Subresource Integrity?

This left aside, in the past I used this approach. Call the parent element with an additional attribute/parameter data-nonce and reuse this nonce on all instances created by the parent.

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

No branches or pull requests

2 participants