Description
Based on the JCRLT-99 i searched the code base for additional places where access to the root node is required.
tripod, in the attached filevault_root_access.txt you can find the complete result for searching the jcrvlt code base for getRootNode. some seemed to be valid shortcuts (marked with (excluded)) but i suspect that others might require some attention.
if using the functionality provided with a non-admin session, access to the root node is likely to not be granted thus rendering the filevault unusable (or risking privilege escalations by being forced to grant a non-privileged session full access up to the root node).
i will create individual subtasks for the various parts that IMHO need to be fixed.
Attachments
Attachments
Issue Links
- is a clone of
-
JCRVLT-99 Creating a package using package manager API requires read access to root node
- Closed
1.
|
Creating a package using package manager API requires read access to root node | Closed | Tobias Bocanegra | |
2.
|
Importer.TxInfo : access to root node | Closed | Unassigned | |
3.
|
DefaultWorkspaceFilter requires access to root node | Closed | Unassigned | |
4.
|
JcrPackageDefinitionImpl always accesses root node | Closed | Unassigned | |
5.
|
Access to root node in DocViewSAXImporter and JcrSysViewTransformer | Closed | Unassigned |