[
https://issues.apache.org/jira/browse/SLING-10281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325901#comment-17325901
]
Bertrand Delacretaz commented on SLING-10281:
---------------------------------------------
Thank you for the explanation I wasn't aware of those configurable paths for
principal-based permissions.
I have added a comment in the PR explaining my suggested changes,
[https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/14/files#r616781576]
Thanks for the different behavior reference, that works for me!
> Revert changes from SLING-9449
> ------------------------------
>
> 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: 4h 50m
> 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)
