[
https://issues.apache.org/jira/browse/GROOVY-6906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Milles updated GROOVY-6906:
--------------------------------
Description:
Sometimes you want to execute untrusted scripts in a GroovyShell and want to
prevent them from using {{System.exit()}}, reading or writing files and system
properties, starting threads and whatnot.
You could do this via Java's SecurityManager, but doing so is quite cumbersome
as it does not even have the option of applying security settings on a
per-thread basis.
It would be great if Groovy offered a way to specify a set of {{Permission}}
objects for a {{Script}}'s execution.
was:
Sometimes you want to execute untrusted scripts in a GroovyShell and want to
prevent them from using {{System.exit()}}, reading or writing files and system
properties, starting threads and whatnot.
You could do this via Java's SecurityManager, but doing so is quite cumbersome
as it does not even have the option of applying security settings on a
per-thread basis.
It would be great if Groovy offered a way to specify a set of {{Permission}}s
for a {{Script}}'s execution.
> It should be possible to specify permissions for a script
> ---------------------------------------------------------
>
> Key: GROOVY-6906
> URL: https://issues.apache.org/jira/browse/GROOVY-6906
> Project: Groovy
> Issue Type: Wish
> Affects Versions: 2.3.3
> Reporter: Jochen Kemnade
> Priority: Major
>
> Sometimes you want to execute untrusted scripts in a GroovyShell and want to
> prevent them from using {{System.exit()}}, reading or writing files and
> system properties, starting threads and whatnot.
> You could do this via Java's SecurityManager, but doing so is quite
> cumbersome as it does not even have the option of applying security settings
> on a per-thread basis.
> It would be great if Groovy offered a way to specify a set of {{Permission}}
> objects for a {{Script}}'s execution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
