Plugin fails strict CSP configurations
-
The SiteKit plugin requires a less secure Content Security Policy configuration to accommodate its use of new Function throughout its scripts, specifically this one:
google-site-kit/dist/assets/js/googlesitekit-vendor-e44f66f39f4394756bf1.jsCSP doesn’t allow the ‘unsafe-eval’ attribute to be scoped per domain or script origin, meaning enabling it globally would weaken the security posture for the entire site. We’re aiming to maintain strong security standards with our site, and at the same time we enjoy the features of your plugin.
I’d like to request that future versions of the plugin avoid reliance on eval-like functions such as new Function(), allowing the plugin to run without compromising more secure CSP configurations.
Are there plans in place already for making this update? Will you consider adding this update to a near future update of the plugin?
Thanks for your time!
The page I need help with: [log in to see the link]
The topic ‘Plugin fails strict CSP configurations’ is closed to new replies.