[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4337:
----------------------------------
Attachment: LUCENE-4337-not-working.patch
Just for completeness: I add here my ideas to create an AllButPermission (a
Permission that grants everything, except a dynamically configureable list of
Permission classes). The class is quite big and the small improvement of the
policy file does not really make this a good alternative (although it would be
cool). Unfortunately the patch works if you use the Permission directly in Java
code, but from the policy file it is simply ignored. From my studies it looks
like a Permission class must be in a signed code base to be used by the policy
parser (like rt.jar).
Maybe Greg, you can use that as an improvement to your class.
> 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.0-BETA
> Reporter: Greg Bowyer
> Assignee: Uwe Schindler
> Fix For: 5.0, 4.0
>
> Attachments: ChrootSecurityManager.java,
> ChrootSecurityManagerTest.java, LUCENE-4337-not-working.patch,
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
