Issue #18 wontfix

secure groovy console to avoid System.exit

Anonymous created an issue

Comments (4)

  1. Zemian Deng

    Thanks for the link.

    I will consider this, however I intended the script engine to be fully utilized in the scheduler though; without any restriction. The scheduler application is usually intend to be run as server components, so this shouldn't pose much trouble since it shouldn't be open to any public access. If the user/admin wants to deploy scheduler with such restriction, they can always just use the Java sanbox model (java.lang.SecurityManager).

  2. Log in to comment