[
https://issues.apache.org/jira/browse/SLING-10281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364186#comment-17364186
]
Bertrand Delacretaz commented on SLING-10281:
---------------------------------------------
PR #14 is back in sync but as discussed there there's some instability in the
tests - while the current tests at
[https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-jcr-repoinit/job/master/]
are stable.
I'd like to get a release out and don't have much time to look at this now so
I'll move this ticket to the next release. We can always do another release one
this is fixed.
> Revert SLING-9449: set principal ACL should throw an Exception it it fails
> --------------------------------------------------------------------------
>
> Key: SLING-10281
> URL: https://issues.apache.org/jira/browse/SLING-10281
> Project: Sling
> Issue Type: Bug
> Components: Repoinit
> Affects Versions: Repoinit JCR 1.1.34
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Repoinit JCR 1.1.36
>
> Time Spent: 7h
> Remaining Estimate: 0h
>
> As highlighted in the last comment of SLING-9449, repoinit should use
> exceptions when some statements cannot be applied (as that leads to an
> undesired repository state). In the worst case it could lead to privilege
> escalation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
