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.

Sign up for GitHub

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

Jump to bottom

Document a working Content-Security-Policy #9638

Open
2 tasks done
pabzm opened this issue Sep 16, 2024 · 2 comments · May be fixed by #9665
Open
2 tasks done

Document a working Content-Security-Policy #9638

pabzm opened this issue Sep 16, 2024 · 2 comments · May be fixed by #9665
Assignees
@pabzm
Labels
C: Documentation

Comments

@pabzm
Copy link
Member

pabzm commented Sep 16, 2024

Prerequisites

  • I have searched for duplicate or closed feature requests
  • I have searched for plugins that provide already provide the feature

Proposal

We should document a Content-Security-Policy, that is a strict as possible without breaking any usage of Roundcube.

Motivation and context

These days, CSPs are a relevant part of web security. We should help people with that. It might also reduce the number of issues in which people have problems due to a CSP, or having questions about it.
@pabzm
Copy link
Member Author

pabzm commented Sep 16, 2024

This was inspired by #9634

@pabzm pabzm self-assigned this Sep 16, 2024
@pabzm
Copy link
Member Author

pabzm commented Sep 16, 2024

We could start to include a CSP in all our HTTP Headers, too, and then send a stricter one unless remote objects are allowed!

@pabzm pabzm linked a pull request Oct 7, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pabzm pabzm

Labels
C: Documentation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Send a configurable CSP in every HTML response pabzm/roundcubemail
1 participant
@pabzm