[
https://issues.apache.org/jira/browse/SLING-10953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17471887#comment-17471887
]
Robert Munteanu commented on SLING-10953:
-----------------------------------------
My personal preference would be to be able to consume AntiSamy 1.6.5 with a
discovery mechanism that does not work for us. However, we can always fall back
( for 1.6.4 at least ) to providing a custom transformer factory. I've prepared
a draft PR that should work -
https://github.com/apache/sling-org-apache-sling-xss/pull/12
> Update dependency Antisamy version from 1.5.10 to 1.6.4
> -------------------------------------------------------
>
> Key: SLING-10953
> URL: https://issues.apache.org/jira/browse/SLING-10953
> Project: Sling
> Issue Type: Improvement
> Reporter: Tatyana Vogel
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: XSS Protection API 2.2.18
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The latest version of AntiSamy is 1.6.4, see
> https://search.maven.org/search?q=g:org.owasp.antisamy%20AND%20a:antisamy .
> We should upgrade to that version, since we embed the AntiSamy bundle and
> there is no other way for consumers of the bundle to upgrade.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
