praktomat.policy vs java.policy

[chris21k]

Praktomat/src/checker/checker/DejaGnu.py line 120 references not existing file "praktomat.policy" instead of in directory Praktomat/src/checker/scripts/ supplied "java.policy". Thus, 'spawn java' starts a jvm with empty policies via Praktomat/src/checker/scripts/java. A workaround without touching the python code is
$ ln -s java.policy praktomat.policy
in this directory.

[ifrh]

Just found on https://docs.oracle.com/en/java/javase/17/security/java-security-overview1.html#GUID-BBEC2DC8-BA00-42B1-B52A-A49488FCF8FE

The Security Manager and APIs related to it have been deprecated and are subject to removal in a future release. There is no replacement for the Security Manager. See JEP 411 - https://openjdk.java.net/jeps/411 - for discussion and alternatives.

corresponding information here:
https://bugs.openjdk.java.net/browse/JDK-8264713

[ifrh]

@chris21k could you please update the issue headline, that one can read, that Security Manager is deprecated?

referencing to an old mail to praktomat mailinglist (8.10.2016 of @nomeata ), perhaps firejail https://firejail.wordpress.com/ could use as sandbox i.e. on systems where Docker containers are "too big".

[ifrh]

Implementation changed to

Praktomat/src/checker/checker/DejaGnu.py

Line 122 in 92d1cf5

environ['POLICY'] = join(script_dir, "java.policy")

via commit bc585cf#diff-e64c26e50d196ca3f4cccef7ec36c569a692481cafc1b02a789b44f321e7e590 merged to master