[jira] [Commented] (DERBY-7138) Remove references to the Java Security Manager
[ https://issues.apache.org/jira/browse/DERBY-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522521#comment-17522521 ] ASF subversion and git services commented on DERBY-7138: Commit 1899867 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1899867 ] DERBY-7138: Remove the no longer needed SecurityManagerSetup test class; commit derby-7138-06-aa-removeSecurityManagerSetup.diff. > Remove references to the Java Security Manager > -- > > Key: DERBY-7138 > URL: https://issues.apache.org/jira/browse/DERBY-7138 > Project: Derby > Issue Type: Task > Components: Build tools, Documentation >Affects Versions: 10.16.0.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: DerbyServerTest.java, Z.java, > derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.diff, > derby-7138-02-ab-moveMethodsToTestConfiguration.diff, > derby-7138-03-aa-removePermissionsTests.diff, > derby-7138-04-ab-hostChangeInNetworkServerControlApiTest.diff, > derby-7138-05-aa-removeSecurityManager.diff, > derby-7138-06-aa-removeSecurityManagerSetup.diff > > > The Open JDK team has deprecated the Java Security Manager and indicated that > it will be removed in a future release of Java. See > https://openjdk.java.net/jeps/411. In an email thread titled "protecting > security-sensitive operations on multi-tenant servers" on the > security-...@openjdk.java.net mailing list, Alan Bateman indicated that > developers should containerize their applications instead. > This issue tracks work needed to remove Derby's references to the Java > Security Manager. > At a minimum, the following work needs to be done: > o The tests should be adjusted so that they don't install a SecurityManager. > o References to the SecurityManager should be removed from product code. > o We should remove the SecurityManager section of the Derby Security Guide. > In its place, we should recommend that developers containerize their Derby > applications. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (DERBY-7138) Remove references to the Java Security Manager
[
https://issues.apache.org/jira/browse/DERBY-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522520#comment-17522520
]
Richard N. Hillegas edited comment on DERBY-7138 at 4/14/22 7:56 PM:
-
Attaching derby-7138-06-aa-removeSecurityManagerSetup.diff. This patch removes
the SecurityManagerTest class, used for testing. With this patch, tests passed
cleanly with both the classpath and the modulepath.
Touches the following files:
{noformat}
D
java/org.apache.derby.tests/org/apache/derbyTesting/junit/SecurityManagerSetup.java
Delete this class of support methods.
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/harness/jvm.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/BaseTestCase.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/NetworkServerTestSetup.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/TestConfiguration.java
Remove references to the deleted class.
{noformat}
was (Author: rhillegas):
Attaching derby-7138-06-aa-removeSecurityManagerSetup.diff. This patch removes
the SecurityManagerTest class, used for testing. With this patch, tests passed
cleanly with both the classpath and the modulepath.
Touches the following files:
{noformat}
D
java/org.apache.derby.tests/org/apache/derbyTesting/junit/SecurityManagerSetup.java
Delete this class of support methods.
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/harness/jvm.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/BaseTestCase.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/NetworkServerTestSetup.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/TestConfiguration.java
Remove references to the deleted class.
{noformat
> Remove references to the Java Security Manager
> --
>
> Key: DERBY-7138
> URL: https://issues.apache.org/jira/browse/DERBY-7138
> Project: Derby
> Issue Type: Task
> Components: Build tools, Documentation
>Affects Versions: 10.16.0.0
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: DerbyServerTest.java, Z.java,
> derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.diff,
> derby-7138-02-ab-moveMethodsToTestConfiguration.diff,
> derby-7138-03-aa-removePermissionsTests.diff,
> derby-7138-04-ab-hostChangeInNetworkServerControlApiTest.diff,
> derby-7138-05-aa-removeSecurityManager.diff,
> derby-7138-06-aa-removeSecurityManagerSetup.diff
>
>
> The Open JDK team has deprecated the Java Security Manager and indicated that
> it will be removed in a future release of Java. See
> https://openjdk.java.net/jeps/411. In an email thread titled "protecting
> security-sensitive operations on multi-tenant servers" on the
> security-...@openjdk.java.net mailing list, Alan Bateman indicated that
> developers should containerize their applications instead.
> This issue tracks work needed to remove Derby's references to the Java
> Security Manager.
> At a minimum, the following work needs to be done:
> o The tests should be adjusted so that they don't install a SecurityManager.
> o References to the SecurityManager should be removed from product code.
> o We should remove the SecurityManager section of the Derby Security Guide.
> In its place, we should recommend that developers containerize their Derby
> applications.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (DERBY-7138) Remove references to the Java Security Manager
[
https://issues.apache.org/jira/browse/DERBY-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522520#comment-17522520
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-06-aa-removeSecurityManagerSetup.diff. This patch removes
the SecurityManagerTest class, used for testing. With this patch, tests passed
cleanly with both the classpath and the modulepath.
Touches the following files:
{noformat}
D
java/org.apache.derby.tests/org/apache/derbyTesting/junit/SecurityManagerSetup.java
Delete this class of support methods.
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/harness/jvm.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/BaseTestCase.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/NetworkServerTestSetup.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/TestConfiguration.java
Remove references to the deleted class.
{noformat
> Remove references to the Java Security Manager
> --
>
> Key: DERBY-7138
> URL: https://issues.apache.org/jira/browse/DERBY-7138
> Project: Derby
> Issue Type: Task
> Components: Build tools, Documentation
>Affects Versions: 10.16.0.0
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Attachments: DerbyServerTest.java, Z.java,
> derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.diff,
> derby-7138-02-ab-moveMethodsToTestConfiguration.diff,
> derby-7138-03-aa-removePermissionsTests.diff,
> derby-7138-04-ab-hostChangeInNetworkServerControlApiTest.diff,
> derby-7138-05-aa-removeSecurityManager.diff,
> derby-7138-06-aa-removeSecurityManagerSetup.diff
>
>
> The Open JDK team has deprecated the Java Security Manager and indicated that
> it will be removed in a future release of Java. See
> https://openjdk.java.net/jeps/411. In an email thread titled "protecting
> security-sensitive operations on multi-tenant servers" on the
> security-...@openjdk.java.net mailing list, Alan Bateman indicated that
> developers should containerize their applications instead.
> This issue tracks work needed to remove Derby's references to the Java
> Security Manager.
> At a minimum, the following work needs to be done:
> o The tests should be adjusted so that they don't install a SecurityManager.
> o References to the SecurityManager should be removed from product code.
> o We should remove the SecurityManager section of the Derby Security Guide.
> In its place, we should recommend that developers containerize their Derby
> applications.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (DERBY-7138) Remove references to the Java Security Manager
[ https://issues.apache.org/jira/browse/DERBY-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard N. Hillegas updated DERBY-7138: --- Attachment: derby-7138-06-aa-removeSecurityManagerSetup.diff > Remove references to the Java Security Manager > -- > > Key: DERBY-7138 > URL: https://issues.apache.org/jira/browse/DERBY-7138 > Project: Derby > Issue Type: Task > Components: Build tools, Documentation >Affects Versions: 10.16.0.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: DerbyServerTest.java, Z.java, > derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.diff, > derby-7138-02-ab-moveMethodsToTestConfiguration.diff, > derby-7138-03-aa-removePermissionsTests.diff, > derby-7138-04-ab-hostChangeInNetworkServerControlApiTest.diff, > derby-7138-05-aa-removeSecurityManager.diff, > derby-7138-06-aa-removeSecurityManagerSetup.diff > > > The Open JDK team has deprecated the Java Security Manager and indicated that > it will be removed in a future release of Java. See > https://openjdk.java.net/jeps/411. In an email thread titled "protecting > security-sensitive operations on multi-tenant servers" on the > security-...@openjdk.java.net mailing list, Alan Bateman indicated that > developers should containerize their applications instead. > This issue tracks work needed to remove Derby's references to the Java > Security Manager. > At a minimum, the following work needs to be done: > o The tests should be adjusted so that they don't install a SecurityManager. > o References to the SecurityManager should be removed from product code. > o We should remove the SecurityManager section of the Derby Security Guide. > In its place, we should recommend that developers containerize their Derby > applications. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DERBY-7138) Remove references to the Java Security Manager
[ https://issues.apache.org/jira/browse/DERBY-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522339#comment-17522339 ] ASF subversion and git services commented on DERBY-7138: Commit 1899857 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1899857 ] DERBY-7138: Turn off the SecurityManager and no longer use it in tests; commit derby-7138-05-aa-removeSecurityManager.diff. > Remove references to the Java Security Manager > -- > > Key: DERBY-7138 > URL: https://issues.apache.org/jira/browse/DERBY-7138 > Project: Derby > Issue Type: Task > Components: Build tools, Documentation >Affects Versions: 10.16.0.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: DerbyServerTest.java, Z.java, > derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.diff, > derby-7138-02-ab-moveMethodsToTestConfiguration.diff, > derby-7138-03-aa-removePermissionsTests.diff, > derby-7138-04-ab-hostChangeInNetworkServerControlApiTest.diff, > derby-7138-05-aa-removeSecurityManager.diff > > > The Open JDK team has deprecated the Java Security Manager and indicated that > it will be removed in a future release of Java. See > https://openjdk.java.net/jeps/411. In an email thread titled "protecting > security-sensitive operations on multi-tenant servers" on the > security-...@openjdk.java.net mailing list, Alan Bateman indicated that > developers should containerize their applications instead. > This issue tracks work needed to remove Derby's references to the Java > Security Manager. > At a minimum, the following work needs to be done: > o The tests should be adjusted so that they don't install a SecurityManager. > o References to the SecurityManager should be removed from product code. > o We should remove the SecurityManager section of the Derby Security Guide. > In its place, we should recommend that developers containerize their Derby > applications. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DERBY-7138) Remove references to the Java Security Manager
[ https://issues.apache.org/jira/browse/DERBY-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522309#comment-17522309 ] Bryan Pendleton commented on DERBY-7138: Delete that code! Delete that code! Delete that code! Yay! > Remove references to the Java Security Manager > -- > > Key: DERBY-7138 > URL: https://issues.apache.org/jira/browse/DERBY-7138 > Project: Derby > Issue Type: Task > Components: Build tools, Documentation >Affects Versions: 10.16.0.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Attachments: DerbyServerTest.java, Z.java, > derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.diff, > derby-7138-02-ab-moveMethodsToTestConfiguration.diff, > derby-7138-03-aa-removePermissionsTests.diff, > derby-7138-04-ab-hostChangeInNetworkServerControlApiTest.diff, > derby-7138-05-aa-removeSecurityManager.diff > > > The Open JDK team has deprecated the Java Security Manager and indicated that > it will be removed in a future release of Java. See > https://openjdk.java.net/jeps/411. In an email thread titled "protecting > security-sensitive operations on multi-tenant servers" on the > security-...@openjdk.java.net mailing list, Alan Bateman indicated that > developers should containerize their applications instead. > This issue tracks work needed to remove Derby's references to the Java > Security Manager. > At a minimum, the following work needs to be done: > o The tests should be adjusted so that they don't install a SecurityManager. > o References to the SecurityManager should be removed from product code. > o We should remove the SecurityManager section of the Derby Security Guide. > In its place, we should recommend that developers containerize their Derby > applications. -- This message was sent by Atlassian Jira (v8.20.1#820001)
