[
https://issues.apache.org/jira/browse/JDO-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tilmann Zäschke updated JDO-816:
--------------------------------
Description:
Use Java 9 modules to simplify code and improve JDO security.
The deprecation of the Java securityManager in Java 18 was handled in
[JDO-808|https://issues.apache.org/jira/browse/JDO-808] by adding a class
LegacyJava as well as numerous doPrivileged() in the JDO API.
Using Java 9 modules we could:
- remove the code duplication
- better protect the LegacyJava class (it should be safe, but it is a manually
implemented security feature, which is never good)
Alternative / Reason why we might NOT do it:
- The rationale for removing the SecurityManager is that it does not protect
against a real world attach vector. Using this argument we could simply remove
LegacyJava and all associated classes and code.
was:
Use Java 9 modules to simplify code and improve JDO security.
The deprecation of the Java securityManager in Java 18 was handled in
[JDO-808|https://issues.apache.org/jira/browse/JDO-808] by adding a class
LegacyJava as well as numerous doPrivileged() in the JDO API.
Using Java 9 modules we could:
- remove the code duplication
- better protect the LegacyJava class (it should be safe, but it is a manually
implemented security feature, which is never good)
Alternative / Reason why we might no to it:
- The rationale for removing the SecurityManager is that it does not protect
against a real world attach vector. Using this argument we could simply remove
LegacyJava and all associated classes and code.
> Use Java 9 modules to protect LegacyJava
> ----------------------------------------
>
> Key: JDO-816
> URL: https://issues.apache.org/jira/browse/JDO-816
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3.2.1
> Reporter: Tilmann Zäschke
> Priority: Minor
> Fix For: JDO 3.3
>
>
> Use Java 9 modules to simplify code and improve JDO security.
> The deprecation of the Java securityManager in Java 18 was handled in
> [JDO-808|https://issues.apache.org/jira/browse/JDO-808] by adding a class
> LegacyJava as well as numerous doPrivileged() in the JDO API.
> Using Java 9 modules we could:
> - remove the code duplication
> - better protect the LegacyJava class (it should be safe, but it is a
> manually implemented security feature, which is never good)
> Alternative / Reason why we might NOT do it:
> - The rationale for removing the SecurityManager is that it does not protect
> against a real world attach vector. Using this argument we could simply
> remove LegacyJava and all associated classes and code.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
