[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=17539001#comment-17539001 ] ASF subversion and git services commented on DERBY-7138: Commit 1901044 from Richard N. Hillegas in branch 'docs/branches/10.16' [ https://svn.apache.org/r1901044 ] DERBY-7138: Merge 1901043 from trunk docs to 10.16 docs. > 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.1.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.16.1.0 > > Attachments: DerbyServerTest.java, Z.java, > derby-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff, > derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff, > derby-7138-22-aa-dontTryToZipUpMissingSecurityPolicies.diff, > derby-7138-23-aa-dontTryToTarUpMissingSecurityPolicies.diff, > derby-7138-24-aa-danglingDocsReference.diff, postSecurityManager.html, > releaseNote.html > > > 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.7#820007)
[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=17539000#comment-17539000 ] ASF subversion and git services commented on DERBY-7138: Commit 1901043 from Richard N. Hillegas in branch 'docs/trunk' [ https://svn.apache.org/r1901043 ] DERBY-7138: Remove dangling references to now-deleted security pages which prevented us from building the pdf version of the Admin Guide; commit derby-7138-24-aa-danglingDocsReference.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.1.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.16.1.0 > > Attachments: DerbyServerTest.java, Z.java, > derby-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff, > derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff, > derby-7138-22-aa-dontTryToZipUpMissingSecurityPolicies.diff, > derby-7138-23-aa-dontTryToTarUpMissingSecurityPolicies.diff, > derby-7138-24-aa-danglingDocsReference.diff, postSecurityManager.html, > releaseNote.html > > > 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.7#820007)
[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=17538998#comment-17538998
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-24-aa-danglingDocsReference.diff. Removed some dangling
references to now-deleted security documentation. The dangling references
prevented us from building the pdf version of the Admin Guide.
Touches the following files:
{noformat}
M src/adminguide/cadminreplication.dita
M src/adminguide/cadminreplicfailures.dita
{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.1.0
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Fix For: 10.16.1.0
>
> Attachments: DerbyServerTest.java, Z.java,
> derby-3547-01-aa-policyGenerator.diff,
> 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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.diff,
> derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff,
> derby-7138-13-aa-adjustUserDocumentation.diff,
> derby-7138-13-aa-adjustUserDocumentation.tar,
> derby-7138-14-aa-removeMoreDocReferences-1.tar,
> derby-7138-14-aa-removeMoreDocReferences.diff,
> derby-7138-14-aa-removeMoreDocReferences.tar,
> derby-7138-16-aa-removeMoreReferences.diff,
> derby-7138-17-ab-securityExceptions.diff,
> derby-7138-18-aa-moreSecurityExceptions.diff,
> derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff,
> derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff,
> derby-7138-22-aa-dontTryToZipUpMissingSecurityPolicies.diff,
> derby-7138-23-aa-dontTryToTarUpMissingSecurityPolicies.diff,
> derby-7138-24-aa-danglingDocsReference.diff, postSecurityManager.html,
> releaseNote.html
>
>
> 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.7#820007)
[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=17538394#comment-17538394 ] ASF subversion and git services commented on DERBY-7138: Commit 1901015 from Richard N. Hillegas in branch 'code/branches/10.16' [ https://svn.apache.org/r1901015 ] DERBY-7138: Merge 1901014 from trunk to 10.16 branch. > 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.1.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.16.1.0 > > Attachments: DerbyServerTest.java, Z.java, > derby-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff, > derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff, > derby-7138-22-aa-dontTryToZipUpMissingSecurityPolicies.diff, > derby-7138-23-aa-dontTryToTarUpMissingSecurityPolicies.diff, > postSecurityManager.html, releaseNote.html > > > 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.7#820007)
[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=17538392#comment-17538392 ] ASF subversion and git services commented on DERBY-7138: Commit 1901014 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1901014 ] DERBY-7138: Remove code which added security policies to the tar distributions; commit derby-7138-23-aa-dontTryToTarUpMissingSecurityPolicies.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.1.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.16.1.0 > > Attachments: DerbyServerTest.java, Z.java, > derby-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff, > derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff, > derby-7138-22-aa-dontTryToZipUpMissingSecurityPolicies.diff, > derby-7138-23-aa-dontTryToTarUpMissingSecurityPolicies.diff, > postSecurityManager.html, releaseNote.html > > > 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.7#820007)
[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=17538391#comment-17538391
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-23-aa-dontTryToTarUpMissingSecurityPolicies.diff.
Similarly, this patch removes the build code which put security policies in the
tar distros.
Touches the following files:
{noformat}
M tools/release/build.xml
{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.1.0
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Fix For: 10.16.1.0
>
> Attachments: DerbyServerTest.java, Z.java,
> derby-3547-01-aa-policyGenerator.diff,
> 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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.diff,
> derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff,
> derby-7138-13-aa-adjustUserDocumentation.diff,
> derby-7138-13-aa-adjustUserDocumentation.tar,
> derby-7138-14-aa-removeMoreDocReferences-1.tar,
> derby-7138-14-aa-removeMoreDocReferences.diff,
> derby-7138-14-aa-removeMoreDocReferences.tar,
> derby-7138-16-aa-removeMoreReferences.diff,
> derby-7138-17-ab-securityExceptions.diff,
> derby-7138-18-aa-moreSecurityExceptions.diff,
> derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff,
> derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff,
> derby-7138-22-aa-dontTryToZipUpMissingSecurityPolicies.diff,
> derby-7138-23-aa-dontTryToTarUpMissingSecurityPolicies.diff,
> postSecurityManager.html, releaseNote.html
>
>
> 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.7#820007)
[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=17538385#comment-17538385 ] ASF subversion and git services commented on DERBY-7138: Commit 1901012 from Richard N. Hillegas in branch 'code/branches/10.16' [ https://svn.apache.org/r1901012 ] DERBY-7138: Merge 1901011 from trunk to 10.16 branch. > 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.1.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.16.1.0 > > Attachments: DerbyServerTest.java, Z.java, > derby-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff, > derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff, > derby-7138-22-aa-dontTryToZipUpMissingSecurityPolicies.diff, > postSecurityManager.html, releaseNote.html > > > 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.7#820007)
[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=17538384#comment-17538384 ] ASF subversion and git services commented on DERBY-7138: Commit 1901011 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1901011 ] DERBY-7138: Remove build code which added security policies to the release distributions; commit derby-7138-22-aa-dontTryToZipUpMissingSecurityPolicies.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.1.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.16.1.0 > > Attachments: DerbyServerTest.java, Z.java, > derby-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff, > derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff, > derby-7138-22-aa-dontTryToZipUpMissingSecurityPolicies.diff, > postSecurityManager.html, releaseNote.html > > > 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.7#820007)
[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=17538382#comment-17538382
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-22-aa-dontTryToZipUpMissingSecurityPolicies.diff. This
patch removes the release generation code which added security policies to the
distributions.
Touches the following files:
{noformat}
M tools/release/build.xml
{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.1.0
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Fix For: 10.16.1.0
>
> Attachments: DerbyServerTest.java, Z.java,
> derby-3547-01-aa-policyGenerator.diff,
> 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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.diff,
> derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff,
> derby-7138-13-aa-adjustUserDocumentation.diff,
> derby-7138-13-aa-adjustUserDocumentation.tar,
> derby-7138-14-aa-removeMoreDocReferences-1.tar,
> derby-7138-14-aa-removeMoreDocReferences.diff,
> derby-7138-14-aa-removeMoreDocReferences.tar,
> derby-7138-16-aa-removeMoreReferences.diff,
> derby-7138-17-ab-securityExceptions.diff,
> derby-7138-18-aa-moreSecurityExceptions.diff,
> derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff,
> derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff,
> derby-7138-22-aa-dontTryToZipUpMissingSecurityPolicies.diff,
> postSecurityManager.html, releaseNote.html
>
>
> 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.7#820007)
[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=17538376#comment-17538376 ] ASF subversion and git services commented on DERBY-7138: Commit 1901006 from Richard N. Hillegas in branch 'code/branches/10.16' [ https://svn.apache.org/r1901006 ] DERBY-7138: Merge 1901005 from trunk to 10.16 branch. > 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.1.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.16.1.0 > > Attachments: DerbyServerTest.java, Z.java, > derby-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff, > derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff, postSecurityManager.html, > releaseNote.html > > > 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.7#820007)
[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=17538372#comment-17538372 ] ASF subversion and git services commented on DERBY-7138: Commit 1901005 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1901005 ] DERBY-7138: Remove the target which copied generated security policies into the Derby Security Guide during release building; commit derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.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.1.0 >Reporter: Richard N. Hillegas >Assignee: Richard N. Hillegas >Priority: Major > Fix For: 10.16.1.0 > > Attachments: DerbyServerTest.java, Z.java, > derby-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff, > derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff, postSecurityManager.html, > releaseNote.html > > > 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.7#820007)
[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=17538371#comment-17538371
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff. This patch removes
the build target which copied generated policy files into the Derby Security
Guide.
Touches the following files:
{noformat}
M build.xml
{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.1.0
>Reporter: Richard N. Hillegas
>Assignee: Richard N. Hillegas
>Priority: Major
> Fix For: 10.16.1.0
>
> Attachments: DerbyServerTest.java, Z.java,
> derby-3547-01-aa-policyGenerator.diff,
> 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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.diff,
> derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff,
> derby-7138-13-aa-adjustUserDocumentation.diff,
> derby-7138-13-aa-adjustUserDocumentation.tar,
> derby-7138-14-aa-removeMoreDocReferences-1.tar,
> derby-7138-14-aa-removeMoreDocReferences.diff,
> derby-7138-14-aa-removeMoreDocReferences.tar,
> derby-7138-16-aa-removeMoreReferences.diff,
> derby-7138-17-ab-securityExceptions.diff,
> derby-7138-18-aa-moreSecurityExceptions.diff,
> derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff,
> derby-7138-21-aa-dontCopyPolicyFilesIntoDocs.diff, postSecurityManager.html,
> releaseNote.html
>
>
> 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.7#820007)
[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=17536384#comment-17536384 ] Bryan Pendleton commented on DERBY-7138: No apologies needed! I think the technique you used was very sensible, and it's exactly the way I would have approached it, had I but your energy. On we go into the future, all is well. > 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-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff, > postSecurityManager.html, releaseNote.html > > > 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.7#820007)
[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=17536319#comment-17536319 ] Richard N. Hillegas commented on DERBY-7138: Hey Bryan. I think I'm done with changes to the code and docs. I'm working on a release note for this issue. I will also write a release note for DERBY-7137. I apologize for the bewildering sequence of patches. I wanted to proceed cautiously. After investing a good two decades in SecurityManager support, there was a fair amount to unwind. Mostly, the code is easier to read without the privilege blocks. More cleanup is possible. I hope that people are not perplexed by certain, now vacuous methods, which used to run security checks. Also, I did not remove the run() methods from certain classes which used to implement privileged actions. Maybe my comments will help people understand some of the peculiar constructions. > 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-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff, > postSecurityManager.html > > > 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.7#820007)
[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=17536289#comment-17536289 ] Bryan Pendleton commented on DERBY-7138: My what a lot of cleanup this has been! It's been very interesting to watch all the incremental progress you've been making, and how many different details there were along the way. I guess that the Security Manager work was accomplished over a decade (or more?), and so it's no surprise that unwinding it has been a fair piece of work. > 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-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff, > postSecurityManager.html > > > 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.7#820007)
[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=17536215#comment-17536215 ] ASF subversion and git services commented on DERBY-7138: Commit 1900841 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1900841 ] DERBY-7138: Fix some javadoc warnings introduced by work on this issue; commit derby-7138-20-aa-fixJavadoc.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-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff, > postSecurityManager.html > > > 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.7#820007)
[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=17536214#comment-17536214
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-20-aa-fixJavadoc.diff. This patch fixes some javadoc
warnings which were introduced by the work done on this issue.
With this patch, the javadoc builds cleanly.
Touches the following files:
{noformat}
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/management/CacheManagerMBeanTest.java
{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-3547-01-aa-policyGenerator.diff,
> 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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.diff,
> derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff,
> derby-7138-13-aa-adjustUserDocumentation.diff,
> derby-7138-13-aa-adjustUserDocumentation.tar,
> derby-7138-14-aa-removeMoreDocReferences-1.tar,
> derby-7138-14-aa-removeMoreDocReferences.diff,
> derby-7138-14-aa-removeMoreDocReferences.tar,
> derby-7138-16-aa-removeMoreReferences.diff,
> derby-7138-17-ab-securityExceptions.diff,
> derby-7138-18-aa-moreSecurityExceptions.diff,
> derby-7138-19-aa-privilegedActions.diff, derby-7138-20-aa-fixJavadoc.diff,
> postSecurityManager.html
>
>
> 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.7#820007)
[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=17536208#comment-17536208 ] ASF subversion and git services commented on DERBY-7138: Commit 1900840 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1900840 ] DERBY-7138: Remove references to more java.security classes; commit derby-7138-19-aa-privilegedActions.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-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, > derby-7138-19-aa-privilegedActions.diff, postSecurityManager.html > > > 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.7#820007)
[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=17536207#comment-17536207
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-19-aa-privilegedActions.diff. This patch removes
references to PrivilegedActions, PrivilegedActionExceptions, and
PrivilegedExceptionActions. Mostly, these were just vacuous imports and stray
(now wrong) comments.
With this patch, tests pass cleanly with both the classpath and modulepath.
Touches the following files:
{noformat}
M
java/org.apache.derby.client/org/apache/derby/client/net/OpenSocketAction.java
M
java/org.apache.derby.commons/org/apache/derby/shared/common/error/StandardException.java
M
java/org.apache.derby.commons/org/apache/derby/shared/common/info/ProductVersionHolder.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/jdbc/InternalDriver.java
M
java/org.apache.derby.engine/org/apache/derby/impl/jdbc/authentication/NativeAuthenticationServiceImpl.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/jce/JCECipherFactory.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/monitor/StorageFactoryService.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/reflect/ReflectClassesJava2.java
M
java/org.apache.derby.engine/org/apache/derby/impl/store/raw/RawStore.java
M
java/org.apache.derby.engine/org/apache/derby/impl/store/raw/data/BaseDataFileFactory.java
M
java/org.apache.derby.engine/org/apache/derby/impl/store/raw/data/EncryptOrDecryptData.java
M
java/org.apache.derby.engine/org/apache/derby/impl/store/raw/data/RAFContainer.java
M
java/org.apache.derby.engine/org/apache/derby/impl/store/raw/data/StreamFileContainer.java
M
java/org.apache.derby.engine/org/apache/derby/impl/store/raw/log/LogToFile.java
M
java/org.apache.derby.server/org/apache/derby/drda/NetworkServerControl.java
M java/org.apache.derby.tools/org/apache/derby/impl/tools/ij/util.java
M
java/org.apache.derby.tools/org/apache/derby/impl/tools/sysinfo/Main.java
{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-3547-01-aa-policyGenerator.diff,
> 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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.diff,
> derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff,
> derby-7138-13-aa-adjustUserDocumentation.diff,
> derby-7138-13-aa-adjustUserDocumentation.tar,
> derby-7138-14-aa-removeMoreDocReferences-1.tar,
> derby-7138-14-aa-removeMoreDocReferences.diff,
> derby-7138-14-aa-removeMoreDocReferences.tar,
> derby-7138-16-aa-removeMoreReferences.diff,
> derby-7138-17-ab-securityExceptions.diff,
> derby-7138-18-aa-moreSecurityExceptions.diff,
> derby-7138-19-aa-privilegedActions.diff, postSecurityManager.html
>
>
> 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.7#820007)
[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=17535067#comment-17535067 ] ASF subversion and git services commented on DERBY-7138: Commit 1900816 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1900816 ] DERBY-7138: Remove more references to SecurityExceptions; commit derby-7138-18-aa-moreSecurityExceptions.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-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, > derby-7138-18-aa-moreSecurityExceptions.diff, postSecurityManager.html > > > 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.7#820007)
[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=17534601#comment-17534601
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-18-aa-moreSecurityExceptions.diff. This patch removes more
straggling references to SecurityExceptions.
With this patch, tests pass cleanly with both the classpath and modulepath.
Touches the following files:
{noformat}
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/ClassLoaderTestSetup.java
M
java/org.apache.derby.tools/org/apache/derby/impl/tools/sysinfo/Main.java
{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-3547-01-aa-policyGenerator.diff,
> 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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.diff,
> derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff,
> derby-7138-13-aa-adjustUserDocumentation.diff,
> derby-7138-13-aa-adjustUserDocumentation.tar,
> derby-7138-14-aa-removeMoreDocReferences-1.tar,
> derby-7138-14-aa-removeMoreDocReferences.diff,
> derby-7138-14-aa-removeMoreDocReferences.tar,
> derby-7138-16-aa-removeMoreReferences.diff,
> derby-7138-17-ab-securityExceptions.diff,
> derby-7138-18-aa-moreSecurityExceptions.diff, postSecurityManager.html
>
>
> 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.7#820007)
[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=17534453#comment-17534453 ] ASF subversion and git services commented on DERBY-7138: Commit 1900787 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1900787 ] DERBY-7138: Remove many references to SecurityExceptions; commit derby-7138-17-ab-securityExceptions.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-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, > derby-7138-17-ab-securityExceptions.diff, postSecurityManager.html > > > 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.7#820007)
[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=17534452#comment-17534452
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-17-ab-securityExceptions.diff. This patch removes some
straggling references to SecurityExceptions.
With this patch, tests pass cleanly with both the classpath and modulepath.
Touches the following files:
{noformat}
M java/build/org/apache/derbyBuild/ClassSizeCrawler.java
M
java/org.apache.derby.client/org/apache/derby/client/net/NetXAResource.java
M
java/org.apache.derby.commons/org/apache/derby/shared/common/info/JVMInfo.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/jdbc/DRDAServerStarter.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/services/loader/ClassInfo.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/services/loader/ClassInspector.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/services/monitor/ModuleFactory.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/services/property/PropertyUtil.java
M
java/org.apache.derby.engine/org/apache/derby/impl/load/ImportReadData.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/jce/JCECipherFactory.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/monitor/BaseMonitor.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/monitor/FileMonitor.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/monitor/StorageFactoryService.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/reflect/JarLoader.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/stream/RollingFileStream.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/stream/RollingFileStreamProvider.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/stream/SingleStream.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/timer/SingletonTimerFactory.java
M
java/org.apache.derby.engine/org/apache/derby/impl/sql/compile/BinaryListOperatorNode.java
M
java/org.apache.derby.engine/org/apache/derby/impl/store/raw/data/RAFContainer.java
M
java/org.apache.derby.engine/org/apache/derby/impl/store/raw/data/StreamFileContainer.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbc4/StatementTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbcapi/AutoloadTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/management/CacheManagerMBeanTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/util/PrivilegedFileOpsForTests.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/unitTests/harness/BasicUnitTestManager.java
{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-3547-01-aa-policyGenerator.diff,
> 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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.diff,
> derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff,
> derby-7138-13-aa-adjustUserDocumentation.diff,
> derby-7138-13-aa-adjustUserDocumentation.tar,
> derby-7138-14-aa-removeMoreDocReferences-1.tar,
> derby-7138-14-aa-removeMoreDocReferences.diff,
> derby-7138-14-aa-removeMoreDocReferences.tar,
> derby-7138-16-aa-removeMoreReferences.diff,
> derby-7138-17-ab-securityExceptions.diff, postSecurityManager.html
>
>
> 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
[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=17532979#comment-17532979 ] ASF subversion and git services commented on DERBY-7138: Commit 1900634 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1900634 ] DERBY-7138: Remove more references to the SecurityManager; commit derby-7138-16-aa-removeMoreReferences.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-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, > derby-7138-16-aa-removeMoreReferences.diff, postSecurityManager.html > > > 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.7#820007)
[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=17532961#comment-17532961
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-16-aa-removeMoreReferences.diff. This patch removes some
straggling references to the SecurityManager.
With this patch, tests pass cleanly with both the classpath and modulepath.
Touches the following files:
{noformat}
M java/org.apache.derby.client/org/apache/derby/client/am/Version.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/monitor/StorageFactoryService.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/store/Derby5582AutomaticIndexStatisticsTest.java
{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-3547-01-aa-policyGenerator.diff,
> 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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.diff,
> derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff,
> derby-7138-13-aa-adjustUserDocumentation.diff,
> derby-7138-13-aa-adjustUserDocumentation.tar,
> derby-7138-14-aa-removeMoreDocReferences-1.tar,
> derby-7138-14-aa-removeMoreDocReferences.diff,
> derby-7138-14-aa-removeMoreDocReferences.tar,
> derby-7138-16-aa-removeMoreReferences.diff, postSecurityManager.html
>
>
> 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.7#820007)
[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=17532411#comment-17532411 ] ASF subversion and git services commented on DERBY-7138: Commit 1900593 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1900593 ] DERBY-7138: Remove more SecurityManager references from the code; commit derby-7138-15-aa-mostRemainingReferences.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-3547-01-aa-policyGenerator.diff, > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences-1.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, postSecurityManager.html > > > 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.7#820007)
[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=17531967#comment-17531967
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-15-aa-mostRemainingReferences.diff. This patch removes
most remaining references to the SecurityManager in the code. Most of the
removed references appeared in comments. There are a few more references which
require a little work to remove. Other than that, the remaining references are
in comments which explain the presence of methods which only exist because they
were once needed by permissions management.
With this patch, tests pass cleanly with both the classpath and modulepath.
Touches the following files:
{noformat}
M
java/org.apache.derby.engine/org/apache/derby/iapi/services/cache/ClassSize.java
M java/org.apache.derby.engine/org/apache/derby/iapi/types/SqlXmlUtil.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/bytecode/d_BCValidate.java
M
java/org.apache.derby.engine/org/apache/derby/impl/services/reflect/JarLoader.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/util/SecurityCheck.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/util/TestRoutines.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/TestConfiguration.java
{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-3547-01-aa-policyGenerator.diff,
> 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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.diff,
> derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff,
> derby-7138-13-aa-adjustUserDocumentation.diff,
> derby-7138-13-aa-adjustUserDocumentation.tar,
> derby-7138-14-aa-removeMoreDocReferences-1.tar,
> derby-7138-14-aa-removeMoreDocReferences.diff,
> derby-7138-14-aa-removeMoreDocReferences.tar, postSecurityManager.html
>
>
> 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.7#820007)
[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=17531758#comment-17531758 ] ASF subversion and git services commented on DERBY-7138: Commit 1900554 from Richard N. Hillegas in branch 'docs/trunk' [ https://svn.apache.org/r1900554 ] DERBY-7138: Remove more SecurityManager references from the user docs; commit derby-7138-14-aa-removeMoreDocReferences.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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, > derby-7138-14-aa-removeMoreDocReferences.diff, > derby-7138-14-aa-removeMoreDocReferences.tar, postSecurityManager.html > > > 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.7#820007)
[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=17531397#comment-17531397
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-14-aa-removeMoreDocReferences.diff and a corresponding
tarball of generated output (derby-7138-14-aa-removeMoreDocReferences.tar).
This patch removes more references to the SecurityManager and policy files from
the Derby user guides.
In the previous patch, I grep'd for the word "manager" in the docs. In this
patch, I grep'd for the phrases "policy" and "Java security". I also skimmed
the security guide looking for other references to Java security.
{noformat}
--
ADMIN GUIDE
M src/adminguide/radminconfigdb2jdrdatracedirectory.dita
"derby.drda.traceDirectory property" section: Remove example permissions
needed for creating a DRDA trace directory.
M src/adminguide/radminjmxdisable.dita
"Disabling access to MBeans" section: Remove material on how to use
the SecurityManager to disable or restrict access to MBeans.
M src/adminguide/radminjmxenablepwd.dita
"Enabling remote JMX with password authentication only" section:
Remove note about SecurityManager permissions.
M src/adminguide/radminjmxtroubleshoot.dita
"Troubleshooting JMX connection issues" section: Remove an index term
related to security policies.
M src/adminguide/tadminadv804410.dita
"Turning on the trace facility" section: Removed material about permissions
needed for Derby to create a trace file.
--
REFERENCE GUIDE
M src/ref/rrefjdbc4_1connection.dita
"java.sql.Connection.abort method" section: Removed material about the
callAbort permission.
M src/ref/rrefproperextdiagsevlevel.dita
"derby.stream.error.extendedDiagSeverityLevel" section: Removed material
about permissions needed for error logging.
--
SECURITY GUIDE
M src/security/cseccsecure41285.dita
"Configuring LDAP authentication" section: Removed material about necessary
permissions.
M src/security/cseccsecure90988.dita
"Using signed jar files" section: Removed material about SecurityManager
permissions.
M src/security/cseccsecuree.dita
"Part Two: Configuring security for Derby" section: Removed bullet item about
customizing the security policy.
M src/security/csecintroderbydefenses.dita
"Derby defenses against threats" section: Removed entry about Java
SecurityManager defenses.
M src/security/csecintromapping.dita
"Defenses mapped to threats" section: Removed entry about Java SecurityManager
defenses.
M src/security/csecintrootherdefenses.dita
"Defenses outside of Derby" section: Added a bullet item about containerization.
M src/security/csecintrosafer.dita
"Designing safer Derby applications" section: Removed bullet item about
security policies.
M src/security/csecputtogether.dita
"Putting it all together" section: Removed reference to the SecurityManager.
M src/security/tseccsecure81850.dita
"Configuring security in an embedded environment" section: Removed item
about configuring the SecurityManager.
M src/security/tseccsecure82556.dita
"Configuring security in a client/server environment" section: Removed item
about configuring the SecurityManager.
{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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.diff,
> derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff,
> derby-7138-13-aa-adjustUserDocumentation.diff,
> derby-7138-13-aa-adjustUserDocumentation.tar,
> derby-7138-14-aa-removeMoreDocReferences.diff,
> derby-7138-14-aa-removeMoreDocReferences.tar, postSecurityManager.html
>
>
> The Open JDK team has deprecated the Java Security Manager and indicated that
> it will be removed in a
[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=17531247#comment-17531247 ] ASF subversion and git services commented on DERBY-7138: Commit 1900516 from Richard N. Hillegas in branch 'docs/trunk' [ https://svn.apache.org/r1900516 ] DERBY-7138: Remove references to the SecurityManager from the user guides; commit derby-7138-13-aa-adjustUserDocumentation.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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, > derby-7138-13-aa-adjustUserDocumentation.diff, > derby-7138-13-aa-adjustUserDocumentation.tar, postSecurityManager.html > > > 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.7#820007)
[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=17530963#comment-17530963
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-13-aa-adjustUserDocumentation.diff and a corresponding
tarball of generated output (derby-7138-13-aa-adjustUserDocumentation.tar).
This patch removes references to the SecurityManager from the Derby user guides.
{noformat}
--
ADMIN GUIDE
M src/adminguide/cadminov825266.dita
Removed a paragraph from the "The Derby Network Server" section.
It explained that the SecurityManager is installed by default.
M src/adminguide/cadminservlet98430.dita
Removed a clause from the "Managing the Derby Network Server remotely
by using the servlet interface" section. The clause recommended that the user
install a SecurityManager.
M src/adminguide/radmindrdahost.dita
Removed a clause from the "derby.drda.host property" section.
The clause recommended that the user install a SecurityManager.
M src/adminguide/radminjmxenablenoauth.dita
Removed a paragraph from the "Enabling remote JMX with no authentication or
SSL" section.
The paragraph explained that the SecurityManager is installed by default.
M src/adminguide/radminjmxenablepwdssl.dita
Removed a paragraph and example code from the "Enabling remote JMX
with password authentication and SSL" section. The paragraph and example
explained that JMX permissions need to be granted when a SecurityManager is
installed.
M src/adminguide/tadmincbdjhhfd.dita
Removed a paragraph from the "Starting the Network Server" section.
The paragraph urged the user to install a SecurityManager.
M src/adminguide/tadminconfig813694.dita
Removed a note from the "Using the NetworkServerControl API" section.
The note urged the user to install a SecurityManager.
D src/adminguide/cadminreplicsecurity.dita
Removed the "Replication and security" section, which explains how to run
Replication under the Java SecurityManager.
D src/adminguide/radminjmxenablepolicy.dita
Removed the "Fine-grained authorization using a security policy" section,
which explains how to run the JMX beans under the Java SecurityManager.
M src/adminguide/derbyadmin.ditamap
Removed deprecated sections from the table of contents.
--
DEVELOPERS GUIDE
M src/devguide/tdevdvlp20349.dita
Removed a paragraph from the "Shutting down the system" section.
The paragraph explained the need for a "deregister the JDBC driver" permission.
M src/devguide/tdevdvlp40464.dita
Removed a paragraph from the "Shutting down Derby or an individual database"
section.
The paragraph explained the need for a "deregister the JDBC driver" permission.
--
GETTING STARTED GUIDE
M src/getstart/twwdactivity2.dita
M src/getstart/twwdactivity4.dita
Removed SecurityManager installation messages from example output
in the "Activity 2: Run SQL using the client driver"
and "Activity 4: Create and run a JDBC program using the client
driver and Network Server" sections.
--
REFERENCE GUIDE
M src/ref/rrefattribderegister.dita
Removed paragraphs from the "deregister=false attribute" section.
The paragraphs discussed the "deregister the JDBC driver" permission
M src/ref/refderby.ditamap
D src/ref/rrefreloadpolicyproc.dita
Removed the section on the SYSCS_UTIL.SYSCS_RELOAD_SECURITY_POLICY system
procedure.
--
SECURITY GUIDE
M src/security/cseccsecure863446.dita
Removed a paragraph about connection permissions from the
"Setting up Derby to use your LDAP directory service" section.
M src/security/csecputstart.dita
Removed the SecurityManager properties from the example and a clause
about the SecurityManager from the "Starting a secured Network Server" section.
M src/security/secderby.ditamap
M src/security/csecpref23947.dita
D src/security/csecjavasecurity.dita
D src/security/csecrunpolicy.dita
D src/security/rsecbasicclient.dita
D src/security/rsecbasicengine.dita
D src/security/rsecbasicserver.dita
D src/security/rsecbasictools.dita
D src/security/rsecpolicysample.dita
D src/security/tsecnetservopen.dita
D src/security/tsecnetservrun.dita
Removed the "Configuring Java security" section and adjusted the table
of contents and "How this guide is organized" section accordingly.
--
TOOLS GUIDE
M src/tools/derbytools.ditamap
D src/tools/rtoolsoptlucenesecman.dita
Removed the "Running the luceneSupport tool with a security manager" section.
{noformat}
> Remove references to the Java Security Manager
>
[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=17527771#comment-17527771 ] Richard N. Hillegas commented on DERBY-7138: Attaching postSecurityManager.html. This webpage describes Derby vulnerabilities in the absence of a SecurityManager. For some vulnerabilities, I suggest mitigations. > 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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff, postSecurityManager.html > > > 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.7#820007)
[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=17526897#comment-17526897 ] ASF subversion and git services commented on DERBY-7138: Commit 1900228 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1900228 ] DERBY-7138: Make SYSCS_RELOAD_SECURITY_POLICY raise an exception saying that the SecurityManager is no longer supported; commit derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.diff, > derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.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.7#820007)
[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=17525344#comment-17525344
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.diff. This patch makes
the SYSCS_UTIL.SYSCS_RELOAD_SECURITY_POLICY() procedure raise an exception
stating that the method no longer does anything because Derby no longer
supports the Java SecurityManager.
I considered removing the procedure entirely. However, I thought this patch's
solution would make for a slightly better user experience for applications
which accidentally invoke the procedure after soft-upgrading from a pre-10.16
release.
With this patch, tests pass cleanly both with the classpath and with the
modulepath. The upgrade tests also pass cleanly using the same starting points
mentioned in the previous submission.
Touches the following files:
{noformat}
M
java/org.apache.derby.commons/org/apache/derby/shared/common/reference/SQLState.java
M
java/org.apache.derby.engine/org/apache/derby/catalog/SystemProcedures.java
M java/org.apache.derby.engine/org/apache/derby/loc/messages.xml
Make the procedure raise an exception.
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/DBOAccessTest.java
Remove the procedure from the list of system routines which do something but
which only the DBO can invoke.
{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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.diff,
> derby-7138-12-aa-SYSCS_RELOAD_SECURITY_POLICY.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.7#820007)
[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=17525056#comment-17525056 ] ASF subversion and git services commented on DERBY-7138: Commit 1900073 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1900073 ] DERBY-7138: Remove references to policy files which no longer exist; also remove the upgrade test for SYSCS_UTIL.SYSCS_RELOAD_SECURITY_POLICY(); commit derby-7138-11-aa-miscCleanup.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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff, > derby-7138-11-aa-miscCleanup.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.7#820007)
[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=17525025#comment-17525025
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-11-aa-miscCleanup.diff. This patch makes the following
changes:
1) Removes unused references to policy files which no longer exist.
2) Removes the upgrade tests for SYSCS_UTIL.SYSCS_RELOAD_SECURITY_POLICY().
With this patch, tests pass cleanly both with the classpath and with the
modulepath.
Touches the following files:
{noformat}
M java/org.apache.derby.engine/org/apache/derby/impl/jdbc/Util.java
M
java/org.apache.derby.server/org/apache/derby/drda/NetworkServerControl.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/harness/jvm.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/GetCurrentPropertiesTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/NetworkServerControlApiTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/RuntimeInfoTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/ServerPropertiesTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbcapi/LDAPAuthenticationTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbcapi/XATest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/LuceneBackupTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/LuceneJarLoadingTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/store/Derby3980DeadlockTest.java
Changes for (1).
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/upgradeTests/Changes10_3.java
Changes for (2).
{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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff,
> derby-7138-11-aa-miscCleanup.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.7#820007)
[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=17524605#comment-17524605 ] ASF subversion and git services commented on DERBY-7138: Commit 1900042 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1900042 ] DERBY-7138: Remove remaining privilege blocks from Derby code; commit derby-7138-10-aa-removeRemainingPrivilegeBlocks.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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.diff, > derby-7138-10-aa-removeRemainingPrivilegeBlocks.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.7#820007)
[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=17524604#comment-17524604
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-10-aa-removeRemainingPrivilegeBlocks.diff. This patch
removes the remaining privilege blocks from Derby code.
With this patch, tests pass cleanly both with the classpath and with the
modulepath.
Touches the following files:
{noformat}
M
java/org.apache.derby.engine/org/apache/derby/impl/sql/compile/OptimizerTracer.java
M
java/org.apache.derby.server/org/apache/derby/impl/drda/ClientThread.java
M
java/org.apache.derby.server/org/apache/derby/impl/drda/NetworkServerControlImpl.java
{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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.diff,
> derby-7138-09-aa-removeMostProductPrivilegeFiles.diff,
> derby-7138-10-aa-removeRemainingPrivilegeBlocks.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.7#820007)
[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=17524355#comment-17524355 ] ASF subversion and git services commented on DERBY-7138: Commit 1900040 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1900040 ] DERBY-7138: Remove most privilege blocks from product code; commit derby-7138-09-aa-removeMostProductPrivilegeFiles.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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.diff, > derby-7138-09-aa-removeMostProductPrivilegeFiles.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.7#820007)
[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=17523961#comment-17523961
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-09-aa-removeMostProductPrivilegeFiles.diff. This patch
removes privilege blocks from the product code except for the following classes
(to be addressed in a later patch):
{noformat}
trunk/java/org.apache.derby.server/org/apache/derby/impl/drda/NetworkServerControlImpl.java
trunk/java/org.apache.derby.server/org/apache/derby/impl/drda/ClientThread.java
trunk/java/org.apache.derby.engine/org/apache/derby/impl/sql/compile/OptimizerTracer.java
{noformat}
With this patch, tests pass cleanly both with the classpath and with the
modulepath.
Touches the following files:
{noformat}
M
java/org.apache.derby.client/org/apache/derby/client/BasicClientDataSource.java
M
java/org.apache.derby.client/org/apache/derby/client/am/ClientConnection.java
M
java/org.apache.derby.client/org/apache/derby/client/am/Configuration.java
M java/org.apache.derby.client/org/apache/derby/client/net/NetAgent.java
M
java/org.apache.derby.client/org/apache/derby/client/net/OpenSocketAction.java
M
java/org.apache.derby.commons/org/apache/derby/shared/common/error/ExceptionUtil.java
M
java/org.apache.derby.commons/org/apache/derby/shared/common/i18n/MessageService.java
M
java/org.apache.derby.commons/org/apache/derby/shared/common/info/JVMInfo.java
M
java/org.apache.derby.commons/org/apache/derby/shared/common/info/ProductVersionHolder.java
M
java/org.apache.derby.commons/org/apache/derby/shared/common/reference/ModuleUtil.java
M
java/org.apache.derby.commons/org/apache/derby/shared/common/sanity/AssertFailure.java
M
java/org.apache.derby.engine/org/apache/derby/catalog/Java5SystemProcedures.java
M
java/org.apache.derby.engine/org/apache/derby/catalog/SystemProcedures.java
M java/org.apache.derby.engine/org/apache/derby/diag/DiagUtil.java
M java/org.apache.derby.engine/org/apache/derby/diag/ErrorLogReader.java
M java/org.apache.derby.engine/org/apache/derby/diag/ErrorMessages.java
M java/org.apache.derby.engine/org/apache/derby/diag/StatementCache.java
M
java/org.apache.derby.engine/org/apache/derby/diag/StatementDuration.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/jdbc/AutoloadedDriver.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/jdbc/DRDAServerStarter.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/jdbc/InternalDriver.java
M java/org.apache.derby.engine/org/apache/derby/iapi/jdbc/JDBCBoot.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/security/SecurityUtil.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/services/cache/ClassSize.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/services/context/ContextService.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/services/context/SystemContext.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/services/io/FormatIdInputStream.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/services/property/PropertyUtil.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/sql/conn/ConnectionUtil.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/sql/dictionary/DataDescriptorGenerator.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/sql/dictionary/IndexRowGenerator.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/sql/dictionary/SPSDescriptor.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/sql/dictionary/TableDescriptor.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/sql/dictionary/TriggerDescriptor.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/store/access/DiskHashtable.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/types/ClobStreamHeaderGenerator.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/types/DataValueFactoryImpl.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/types/NumberDataType.java
M java/org.apache.derby.engine/org/apache/derby/iapi/types/SqlXmlUtil.java
M
java/org.apache.derby.engine/org/apache/derby/iapi/util/InterruptStatus.java
M java/org.apache.derby.engine/org/apache/derby/impl/db/BasicDatabase.java
M
java/org.apache.derby.engine/org/apache/derby/impl/db/DatabaseContextImpl.java
M java/org.apache.derby.engine/org/apache/derby/impl/db/SlaveDatabase.java
M java/org.apache.derby.engine/org/apache/derby/impl/io/CPFile.java
M
java/org.apache.derby.engine/org/apache/derby/impl/jdbc/ConnectionChild.java
M
java/org.apache.derby.engine/org/apache/derby/impl/jdbc/EmbedConnection.java
M
[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=17523367#comment-17523367 ] ASF subversion and git services commented on DERBY-7138: Commit 1899948 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1899948 ] DERBY-7138: Remove the machinery which generates policy files; commit derby-7138-08-aa-removePolicyFiles.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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.diff, > derby-7138-08-aa-removePolicyFiles.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=17523366#comment-17523366
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-08-aa-removePolicyFiles.diff. This patch makes two changes:
1) Removes the machinery which generates policy files.
2) Removes some straggling references to the java.security command-line
properties.
With this patch, tests pass cleanly both with the classpath and with the
modulepath.
Touches the following files:
{noformat}
M build.xml
D java/build/org/apache/derbyBuild/SecurityPolicyGenerator.java
D
java/org.apache.derby.engine/org/apache/derby/security/securityPolicies.xml
M java/org.apache.derby.tests/build.xml
Changes for (1).
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/harness/jvm.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/management/CacheManagerMBeanTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/NetworkServerTestSetup.java
Changes for (2).
{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,
> derby-7138-07-aa-removePrivilegeBlocksFromTests.diff,
> derby-7138-08-aa-removePolicyFiles.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=17523132#comment-17523132 ] ASF subversion and git services commented on DERBY-7138: Commit 1899913 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1899913 ] DERBY-7138: Remove privilege blocks from the tests; commit derby-7138-07-aa-removePrivilegeBlocksFromTests.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, > derby-7138-07-aa-removePrivilegeBlocksFromTests.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=17522974#comment-17522974
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-07-aa-removePrivilegeBlocksFromTests.diff. This patch
removes privilege blocks from the tests. This includes all references to
java.security.AccessController, java.security.PrivilegedAction, and
java.security.PrivilegedActionException. With this patch, tests pass cleanly
with the classpath and with the modulepath.
Touches the following files:
{noformat}
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/compatibility/VersionCombinationConfigurator.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/demo/CheckToursDBTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/ClientSideSystemPropertiesTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/NetworkServerControlApiTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/ProtocolTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/ServerPropertiesTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/engine/ErrorStreamTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/engine/RestrictiveFilePermissionsTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbc4/AbortTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbc4/ConnectionMethodsTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbcapi/DataSourceSerializationTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbcapi/ResultSetStreamTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/ConstraintCharacteristicsTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/DatabaseClassLoadingTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/XplainStatisticsTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/wisconsin.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/management/JMXTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/management/MBeanTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/management/PlatformConnectionGetter.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/store/AutomaticIndexStatisticsTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/store/ClassLoaderBootTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/store/MaxLogNumberRecovery.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/store/OSReadOnlyTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/upgradeTests/UpgradeClassLoader.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/util/CanonTestCase.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/util/DeadlockWatchdog.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/util/FTFileUtil.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/util/IjTestCase.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/util/PrivilegedFileOpsForTests.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/util/PropertyUtil.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/util/T_ConsistencyChecker.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/util/TestRoutines.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/util/TestUtil.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/BaseJDBCTestCase.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/BaseTestCase.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/ClassLoaderTestSetup.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/ClasspathSetup.java
M java/org.apache.derby.tests/org/apache/derbyTesting/junit/EnvTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/JDBCDataSource.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/LocaleTestSetup.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/NetworkServerTestSetup.java
M
[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] [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] [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)
[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=17522001#comment-17522001
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-05-aa-removeSecurityManager.diff. This patch makes the
following changes:
1) Make the network server no longer install a SecurityManager.
2) Adjust the JUnit tests so that they no longer install a SecurityManager.
3) Remove a couple, straggling permissions tests not included in the previous
derby-7138-03-aa-removePermissionsTests.diff checkin.
With this patch, tests passed cleanly with both the classpath and modulepath.
Touches the following files:
{noformat}
M
java/org.apache.derby.server/org/apache/derby/drda/NetworkServerControl.java
Changes necessary for (1).
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/compatibility/_Suite.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/GetCurrentPropertiesTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/NetworkServerControlApiTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/NetworkServerControlClientCommandTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/ProtocolTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/RuntimeInfoTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/SSLTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/ServerPropertiesTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/SysinfoTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbc4/Driver40UnbootedTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbcapi/AutoloadTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbcapi/InvalidLDAPServerAuthenticationTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbcapi/LDAPAuthenticationTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/jdbcapi/XATest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/AggregateClassLoadingTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/DBInJarTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/DatabaseClassLoadingTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/Derby5652.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/HalfCreatedDatabaseTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/LuceneBackupTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/LuceneCoarseAuthorizationTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/LuceneCollationTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/LuceneInMemoryTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/LuceneJarLoadingTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/LuceneSupportTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/NewOptimizerOverridesTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/RawDBReaderTest.java
D
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/RoutineSecurityTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/SysDiagVTIMappingTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/TriggerGeneralTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/VetJigsawTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/XMLXXETest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/_Suite.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/management/CacheManagerMBeanTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/management/MBeanTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/replicationTests/Derby5937SlaveShutdownTest.java
M
[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=17521715#comment-17521715 ] ASF subversion and git services commented on DERBY-7138: Commit 1899814 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1899814 ] DERBY-7138: Make NetworkServerControlApiTest work without a SecurityManager; commit derby-7138-04-ab-hostChangeInNetworkServerControlApiTest.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 > > > 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=17521332#comment-17521332
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-04-ab-hostChangeInNetworkServerControlApiTest.diff. This
patch addresses the issue raised by the previous comment. This patch changes
the way that NetworkServerControlApiTest identifies the host machine. This
patch also changes that test so that it no longer installs a SecurityManager.
With this patch, the Derby tests pass cleanly with both the classpath and the
modulepath.
Touches the following files:
{noformat}
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/NetworkServerControlApiTest.java
Disables the SecurityManager in this test. Creates NetworkServerControl objects
with the loopback host InetAddress.getByName("localhost") rather than the
actual machine host name InetAddress.getLocalHost().
{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
>
>
> 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=17520824#comment-17520824
]
Richard N. Hillegas commented on DERBY-7138:
Attaching org.apache.derbyTesting.functionTests.tests.derbynet.Z. This test
demonstrates the following:
1) When you bring up a Derby JUnit test with a SecurityManager, then the
NetworkServerControl.getMaxThreads() method behaves correctly, regardless of
whether you create the NetworkServerControl with host set to the loopback
address InetAddress.getByName("localhost") or with host set to the real host
name InetAddress.getLocalHost().
2) However, when you bring up the test WITHOUT a SecurityManager, then
NetworkServerControl.getMaxThreads() fails with a "Connection refused"
exception if you create the NetworkServerControl with the real host name
InetAddress.getLocalHost().
I tripped across this behavior in
NetworkServerControlApiTest.test_04_MaxThreads_0() when I changed the test to
NOT bring up a SecurityManager.
Maybe this behavior is caused by something environmental on my machine.
I am also attaching DerbyServerTest. This program demonstrates that
NetworkServerControl.getMaxThreads() behaves correctly provided that the server
is started with the same host that was used to instantiate NetworkServerControl.
For the record, at my current location
InetAddress.getByName("localhost") is host localhost/127.0.0.1
and
InetAddress.getByName("localhost") is host
Richards-MacBook-Pro-3.local/10.0.0.125
My inclination is to change NetworkServerControlApiTest so that it creates
NetworkServerControl with the loopback address
InetAddress.getByName("localhost").
> 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
>
>
> 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=17516791#comment-17516791 ] Bryan Pendleton commented on DERBY-7138: I *do* love a commit which simply deletes unneeded tests, thanks! > 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: > derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.diff, > derby-7138-02-ab-moveMethodsToTestConfiguration.diff, > derby-7138-03-aa-removePermissionsTests.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=17516505#comment-17516505 ] ASF subversion and git services commented on DERBY-7138: Commit 1899535 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1899535 ] DERBY-7138: Remove tests which just exercise the SecurityManager; commit derby-7138-03-aa-removePermissionsTests.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: > derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.diff, > derby-7138-02-ab-moveMethodsToTestConfiguration.diff, > derby-7138-03-aa-removePermissionsTests.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=17516148#comment-17516148
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-03-aa-removePermissionsTests.diff. This patch removes
tests which obviously only exercise Derby's use of the SecurityManager. With
this patch, the tests pass cleanly with both the classpath and module path.
{noformat}
D
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/SecureServerTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/_Suite.java
D
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/engine/ShutdownWithoutDeregisterPermissionTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/engine/_Suite.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/LuceneSuite.java
D
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/LuceneSupportPermsTest.java
D
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/NoDBInternalsPermissionTest.java
D
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/SecurityPolicyReloadingTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/_Suite.java
D
java/org.apache.derby.tests/org/apache/derbyTesting/unitTests/junit/AssertFailureTest.java
D
java/org.apache.derby.tests/org/apache/derbyTesting/unitTests/junit/MissingPermissionsTest.java
D
java/org.apache.derby.tests/org/apache/derbyTesting/unitTests/junit/SystemPrivilegesPermissionTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/unitTests/junit/_Suite.java
Remove tests which just exercise the SecurityManager.
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/LuceneJarLoadingTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/LuceneSupportTest.java
Relocate some methods out of the deleted LuceneSupportPermsTest.
{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:
> derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.diff,
> derby-7138-02-ab-moveMethodsToTestConfiguration.diff,
> derby-7138-03-aa-removePermissionsTests.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=17516003#comment-17516003 ] ASF subversion and git services commented on DERBY-7138: Commit 1899495 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1899495 ] DERBY-7138: Move some methods and state from SecurityManagerSetup into TestConfiguration; commit derby-7138-02-ab-moveMethodsToTestConfiguration.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: > derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.diff, > derby-7138-02-ab-moveMethodsToTestConfiguration.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=17515613#comment-17515613
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-02-ab-moveMethodsToTestConfiguration.diff. This patch is
an intermediate step on the way to disabling the running of tests under the
SecurityManager. The patch moves some methods from SecurityManagerSetup to
TestConfiguration.
JUnit tests passed cleanly for me with both the classpath and modulepath.
{noformat}
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/SecurityManagerSetup.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/TestConfiguration.java
Move some methods and state from SecurityManagerSet to TestConfiguration.
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/derbynet/SysinfoTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/lang/VetJigsawTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/tools/SysinfoLocaleTest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/tests/tools/derbyrunjartest.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/BaseTestCase.java
M java/org.apache.derby.tests/org/apache/derbyTesting/junit/Derby.java
M
java/org.apache.derby.tests/org/apache/derbyTesting/junit/JAXPFinder.java
Adjust references to the moved items.
{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:
> derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.diff,
> derby-7138-02-ab-moveMethodsToTestConfiguration.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=17514760#comment-17514760 ] ASF subversion and git services commented on DERBY-7138: Commit 1899391 from Richard N. Hillegas in branch 'code/trunk' [ https://svn.apache.org/r1899391 ] DERBY-7138: Revise the old test harness so that it does not use the deprecated Java SecurityManager; commit derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.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: > derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.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=17514191#comment-17514191
]
Richard N. Hillegas commented on DERBY-7138:
Attaching derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.diff. This
patch removes references to the SecurityManager from the old test harness. The
old harness tests run cleanly with this patch.
{noformat}
M
java/org.apache.derby.tests/org/apache/derbyTesting/functionTests/harness/RunTest.java
Remove references to the SecurityManager. Don't install a SecurityManager when
running old harness tests.
{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:
> derby-7138-01-aa-removeSecurityManagerFromOldHarnessTests.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)
