You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Daniel John Debrunner (JIRA)" <de...@db.apache.org> on 2005/08/24 20:59:08 UTC
[jira] Created: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
--------------------------------------------------------------------------------------
Key: DERBY-537
URL: http://issues.apache.org/jira/browse/DERBY-537
Project: Derby
Type: Bug
Components: Security, SQL
Versions: 10.1.1.0
Reporter: Daniel John Debrunner
Assigned to: Daniel John Debrunner
Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508233 ]
Daniel John Debrunner commented on DERBY-537:
---------------------------------------------
Good to have some descriptive comment of how you arrived at that list of changes for the 10.2 backport, since it seems to be a sub-set of the ones listed for the two bugs.
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: https://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Kathey Marsden
> Fix For: 10.3.0.0
>
> Attachments: derby-537_10.2_diff.txt, derby-537_10.2_stat.txt
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-537:
---------------------------------
Attachment: derby-537_10.2_stat.txt
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: https://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Kathey Marsden
> Fix For: 10.3.0.0
>
> Attachments: derby-537_10.2_diff.txt, derby-537_10.2_stat.txt
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-537.
--------------------------------------
Resolution: Fixed
Fix Version/s: 10.2.2.1
10.1.3.2
I don't see anything bad in testing as a result of this. Marking resolved.
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: https://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Kathey Marsden
> Fix For: 10.1.3.2, 10.2.2.1, 10.3.0.0
>
> Attachments: derby-537_10.2_diff.txt, derby-537_10.2_stat.txt, derby-537_10_1_diff.txt
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-537:
---------------------------------
Attachment: derby-537_10.2_diff.txt
This is a port of DERBY-537 and DERBY-538 to 10.2. Changes ported were 387324,473416,473440,473780,473828,473834,474376,482812,482850,483108,483148,483160,483738,484722,543524
Enabled dblook_test.java with security manager to test installation of jar with security manager.
I am running derbyall now and will commit tomorrow if all goes well.
Kathey
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: https://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Kathey Marsden
> Fix For: 10.3.0.0
>
> Attachments: derby-537_10.2_diff.txt, derby-537_10.2_stat.txt
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reopened DERBY-537:
----------------------------------
Assignee: Kathey Marsden (was: Daniel John Debrunner)
reopen for backport
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: https://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Kathey Marsden
> Fix For: 10.3.0.0
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-537?page=comments#action_12449048 ]
Daniel John Debrunner commented on DERBY-537:
---------------------------------------------
Committed revision 473828 to read the jar file in a privileged block.
Still exceptions are thrown with install_jar and replace_jar as writing the jar file into the database jar folder seems to not be under a privileged block.
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: http://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-537:
---------------------------------
Attachment: derby-537_10_1_diff.txt
Here is the 10.1 patch. Running tests now.
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: https://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Kathey Marsden
> Fix For: 10.3.0.0
>
> Attachments: derby-537_10.2_diff.txt, derby-537_10.2_stat.txt, derby-537_10_1_diff.txt
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508311 ]
Kathey Marsden commented on DERBY-537:
--------------------------------------
One question I have about the port is whether the removal of JarFileJava2.java is appropriate for the 10.2 branch. I am running tests with jdk131 to make sure it doesn't create a problem.
Kathey
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: https://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Kathey Marsden
> Fix For: 10.3.0.0
>
> Attachments: derby-537_10.2_diff.txt, derby-537_10.2_stat.txt
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-537:
---------------------------------
Assignee: Daniel John Debrunner (was: Kathey Marsden)
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: https://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Fix For: 10.1.3.2, 10.2.2.1, 10.3.0.0
>
> Attachments: derby-537_10.2_diff.txt, derby-537_10.2_stat.txt, derby-537_10_1_diff.txt
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden closed DERBY-537.
--------------------------------
reclosing this issue
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: https://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Fix For: 10.1.3.2, 10.2.2.1, 10.3.0.0
>
> Attachments: derby-537_10.2_diff.txt, derby-537_10.2_stat.txt, derby-537_10_1_diff.txt
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508594 ]
Kathey Marsden commented on DERBY-537:
--------------------------------------
1.3.1 tests passed with only known failures. So, I will go ahead and check this in in an hour or so unless anyone has comments on the patch.
Kathey
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: https://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Kathey Marsden
> Fix For: 10.3.0.0
>
> Attachments: derby-537_10.2_diff.txt, derby-537_10.2_stat.txt
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-537?page=all ]
Daniel John Debrunner closed DERBY-537.
---------------------------------------
Fix Version/s: 10.3.0.0
Resolution: Fixed
Committed revision 483738
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: http://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Fix For: 10.3.0.0
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-537) SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR
fail when running with a SecurityManager enabled.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508240 ]
Kathey Marsden commented on DERBY-537:
--------------------------------------
I ported all the code changes (I think!) but not all the test changes, because of major test restructuring like the introduction of the JUnit testing infrastructure. I enabled security manager for the dblook_test to test the change in 10.2. If this goes back to 10.1 then I will probably have to test manually or add a network server test since we only test network server under security manager for 10.1
> SQLJ.INSTALL_JAR and SQLJ.UPDATE_JAR fail when running with a SecurityManager enabled.
> --------------------------------------------------------------------------------------
>
> Key: DERBY-537
> URL: https://issues.apache.org/jira/browse/DERBY-537
> Project: Derby
> Issue Type: Bug
> Components: Security, SQL
> Affects Versions: 10.1.1.0
> Reporter: Daniel John Debrunner
> Assignee: Kathey Marsden
> Fix For: 10.3.0.0
>
> Attachments: derby-537_10.2_diff.txt, derby-537_10.2_stat.txt
>
>
> Seen if running the lang/dcl.sql test with a SecurityManager. Accessing the jar file is not within a priviledged block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.