[
https://issues.apache.org/jira/browse/IGNITE-9560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622178#comment-16622178
]
Denis Garus commented on IGNITE-9560:
-------------------------------------
We should:
- add permission(s) for the Distributed Messaging functionality that's
provided via the IgniteMessaging interface;
- split the CACHE_PUT permission to CACHE_PUT for put/putAll operations and
CACHE_INVOKE for cache's set of invoking operations.
> Security permissions to restrict arbitrary code exectution
> ----------------------------------------------------------
>
> Key: IGNITE-9560
> URL: https://issues.apache.org/jira/browse/IGNITE-9560
> Project: Ignite
> Issue Type: Task
> Components: security
> Affects Versions: 2.6
> Reporter: Anton Vinogradov
> Priority: Major
> Fix For: 2.8
>
>
> SecurityPermission class should be extended to cover all cases able to cause
> arbitrary code execution.
> 1) Restriction on listener registration
> - IgniteEvents listener
> - CQ listener
> 2) Restriction on closure (able to be executed on the remote node) execution
> - Compute API (seems to be covered, should be rechecked)
> - Services
> - Entry processor
> 3) We have to make sure that cases listed at #1 and #2 are the all possible
> cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
