-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java security restrictions #350
Comments
@jkrinke : Do you remember where one can find the jar files you mentioned in the year 2002 ? |
This is really old stuff... I indeed found some old scripts that relate to the sandbox and its creation. Please find attached. |
@jkrinke : Thanks for attaching "old.zip".
can you remember what filename was used to fill |
Probably it was ./jre/lib/rt.jar |
add some documentation information into java.policy and junit.policy see KITPraktomatTeam#350 see KITPraktomatTeam#307 closes KITPraktomatTeam#307
In Praktomat/src/checker/scripts/javac there is a german comment containing thoughts about security restrictions at compile and execution time:
Praktomat/src/checker/scripts/java
Lines 1 to 4 in 92d1cf5
Praktomat/src/checker/scripts/javac
Lines 2 to 9 in 92d1cf5
In that comment two
JAR
files are mentioned:I cannot find a trace to this two files and I do not see how they would be used in Praktomat/src/checker/scripts/javac or Praktomat/src/checker/scripts/java .
And in issue #307 it is mentioned that Java's Security Manager is deprecated.
By the way, I think restricted java environments should allow parametrized tests (i.e. JUNIT-PARAMS)
The text was updated successfully, but these errors were encountered: