You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Uwe Schindler (JIRA)" <ji...@apache.org> on 2012/12/16 00:14:13 UTC

[jira] [Created] (LUCENE-4632) Restrict test-framework's write permissions more: Only allow write to per-JVM CWD and the clover.db.dir

Uwe Schindler created LUCENE-4632:
-------------------------------------

             Summary: Restrict test-framework's write permissions more: Only allow write to per-JVM CWD and the clover.db.dir
                 Key: LUCENE-4632
                 URL: https://issues.apache.org/jira/browse/LUCENE-4632
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Uwe Schindler
             Fix For: 4.1, 5.0


Currently we restring wrting to tests.tempDir after SOLR-4195, but it would be better to restrict more and only let child JVMs write to their working dir and not outside (and maybe corrumpt other JVMs).

The problem with current setup is that the child JVM's policy file does not know the runner number nor the absolute working directory (it must be absolute and platform-specific with backslash/slash/... -> new File(".").getAbsolutePath().

Dawid will release a new Junit4 package with a new sysprop passed to every child with its full CWD: junit4.childvm.cwd

In that case the policy file would use this property (and the clover.db.dir) to allow write access and allow only read/execute access for the rest of the  filesystem.

--
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org