[
https://issues.apache.org/jira/browse/WICKET-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825143#comment-13825143
]
Mario Groß edited comment on WICKET-5406 at 11/18/13 7:34 AM:
--------------------------------------------------------------
Yes, but allowing inline JavaScript would kill most of the protection which the
CSP provides. A middle or long-term goal to get rid of the inline scripts in
Wicket would be the better way.
was (Author: magro28):
Yes, but allowing inline JavaScript would kill most of the protection of the
CSP. A middle or long-term goal to get rid of the inline scripts in Wicket
would be the better way.
> Better Content Security Policy Support
> --------------------------------------
>
> Key: WICKET-5406
> URL: https://issues.apache.org/jira/browse/WICKET-5406
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Mario Groß
> Priority: Minor
> Labels: CSP, Content-Security-Policy, Cross-site-Scripting,
> Security
>
> A better support of the Content Security Policy
> (http://en.wikipedia.org/wiki/Content_Security_Policy) would protect against
> cross-site scripting attacks and improve the security image of wicket.
> The main problem at the moment is the heavily used inline javascript code
> which interferes with the whitelisting mechanism of script sources in the CSP
> and should be avoided .
--
This message was sent by Atlassian JIRA
(v6.1#6144)
