Skip to content

Commit a02c1cd

Browse files
committed
Documentation: Add security documentation about CSP (Content Security Policy) headers needing to allow unsafe-inline and unsafe-eval for the inline editor to work - refs #5972
1 parent e1b3af9 commit a02c1cd

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

documentation/security.html

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -184,6 +184,11 @@ <h2><a id="6.HSTS">HTTP Headers Security</a></h2>
184184
but dangerous if you cannot trust people using these features. These features cannot be used by anonymous
185185
users, but portals allowing for open registration could be particularly vulnerable.
186186
</p>
187+
<p>The inline editor in Chamilo 1.11 requires
188+
the Content Security Policy (CSP) headers to include 'unsafe-inline' and 'unsafe-eval'. This is because the
189+
editor includes a number of complex features that require those accesses. This means that your Chamilo install
190+
will probably not validate as an "A+" score in standard CSP tests. We have no solution for this except to
191+
prevent users from using the inline editor, which would remove a considerable level of usability from Chamilo.</p>
187192
<br />
188193
<hr />
189194
<h2><a id="7.Direct-web-access">Direct web access to files</a></h2>

0 commit comments

Comments
 (0)