[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444762#comment-13444762
]
Uwe Schindler commented on LUCENE-4337:
---------------------------------------
Greg,
I have a good idea, that prevents us from really specifying everything in the
policy file: I would only make the AllOtherPermission available in
test-framework and make it take a list of java class names (comma separated) as
parameter. Then it can be added to the default policy file like:
{noformat}
permission org.apache.lucene.utils.AllOtherPermission
"java.io.FilePermission,java.net.SocketPermission,java.security.SecurityPermission";
{noformat}
This would grant (like yours) all other permissions, so only the listed
permissions are added to the policy file. The implies() would only check for
all those classes.
I will come up with a new patch, that simpliefies this!
> Create Java security manager for forcible asserting behaviours in testing
> -------------------------------------------------------------------------
>
> Key: LUCENE-4337
> URL: https://issues.apache.org/jira/browse/LUCENE-4337
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 4.1, 5.0, 4.0
> Reporter: Greg Bowyer
> Assignee: Greg Bowyer
> Attachments: ChrootSecurityManager.java,
> ChrootSecurityManagerTest.java, LUCENE-4337.patch, LUCENE-4337.patch,
> LUCENE-4337.patch
>
>
> Following on from conversations about mutation testing, there is an interest
> in building a Java security manager that is able to assert / guarantee
> certain behaviours
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
