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

Removed unsafe-inline and unsafe-eval #14357

Merged
merged 1 commit into from
Mar 1, 2024
Merged

Conversation

snipe
Copy link
Owner

@snipe snipe commented Mar 1, 2024

This removes the unsafe-inline and unsafe-eval CSP options. I think we had to use those because of vue, but since we don't use vue anymore, we can tighten those down a bit.

Copy link

what-the-diff bot commented Mar 1, 2024

PR Summary

  • Enhanced Security Policy Updates
    The Content Security Policy (CSP), a key player protecting our website from certain cyber threats, has been updated. Specifically, potentially risky values termed 'unsafe-inline' and 'unsafe-eval' were removed from the styling and scripting sections. We also introduced two extra sections: default-src and connect-src to the policy array, fortifying our security measures. These changes reside within the SecurityHeaders.php that is present in the app/Http/Middleware directory.

@snipe snipe merged commit 5b9b21a into develop Mar 1, 2024
4 of 8 checks passed
@snipe snipe deleted the fixes/stricter_csp_rules branch March 1, 2024 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant