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 "Myrna van Lunteren (JIRA)" <de...@db.apache.org> on 2006/01/24 23:05:09 UTC

[jira] Created: (DERBY-871) remote host support in test harness needs more work because of security manager changes

remote host support in test harness needs more work because of security manager changes
---------------------------------------------------------------------------------------

         Key: DERBY-871
         URL: http://issues.apache.org/jira/browse/DERBY-871
     Project: Derby
        Type: Bug
  Components: Test  
    Versions: 10.2.0.0    
    Reporter: Myrna van Lunteren
 Assigned to: Myrna van Lunteren 
    Priority: Minor


With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
permissions need to be passed in derby_test.policy for the client.

-- 
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-871) remote host support in test harness needs more work because of security manager changes

Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-871?page=comments#action_12364390 ] 

Kathey Marsden commented on DERBY-871:
--------------------------------------

Sorry, indicated the wrong bug number, should have said ..

'Can you please offer your ideas on how to organize them for DERBY-871  to not aggravate that situation given the various dependencies and the fact that we will ultimately want to move away from the harness? 


> remote host support in test harness needs more work because of security manager changes
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>  Attachments: DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.

-- 
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] Resolved: (DERBY-871) remote host support in test harness needs more work

Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-871?page=all ]
     
Andrew McIntyre resolved DERBY-871:
-----------------------------------

    Fix Version: 10.2.0.0
     Resolution: Fixed

Committed to trunk with revision 375698.

> remote host support in test harness needs more work
> ---------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: DERBY-871-020606.diff, DERBY-871-020606.stat, DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.
> There is no technical reason for the remote host support to be useprocess=false.
> The readme needs to be updated.
> Also, there are some other changes that have caused for database objects to be left behind, which is a problem because with remote host, databases are re-used.

-- 
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] Closed: (DERBY-871) remote host support in test harness needs more work

Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-871?page=all ]
     
Myrna van Lunteren closed DERBY-871:
------------------------------------


> remote host support in test harness needs more work
> ---------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: DERBY-871-020606.diff, DERBY-871-020606.stat, DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.
> There is no technical reason for the remote host support to be useprocess=false.
> The readme needs to be updated.
> Also, there are some other changes that have caused for database objects to be left behind, which is a problem because with remote host, databases are re-used.

-- 
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-871) remote host support in test harness needs more work because of security manager changes

Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-871?page=all ]

Myrna van Lunteren updated DERBY-871:
-------------------------------------

    Attachment: DERBY-874-012906.stat
                DERBY-874-012906.diff

> remote host support in test harness needs more work because of security manager changes
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>  Attachments: DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.

-- 
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-871) remote host support in test harness needs more work because of security manager changes

Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-871?page=comments#action_12364419 ] 

Daniel John Debrunner commented on DERBY-871:
---------------------------------------------

Thanks Kathey,  leads to three new questions:

1) How are the new properties csinfo.server and csinfo.client different to cs.serverhost and cs.trustedhost?

2) Why is csinfo.trustedhost granted 'connect' permission for derbynet.jar in the testing policy file?
The server isn't connectiing to the client is it?

3) Would csinfo.clienthost be a better name for csinfo.trustedhost? 


Not sure exactly what you are asking of me for property cleanup in DERBY-871, but I think a start is a clear definition of any properties used in the testing policy file. It's possible that the remote testing (even using useProcess=false) does not need any changes to the policy file or the harness. 

> remote host support in test harness needs more work because of security manager changes
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>  Attachments: DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.

-- 
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-871) remote host support in test harness needs more work

Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-871?page=all ]

Myrna van Lunteren updated DERBY-871:
-------------------------------------

        Summary: remote host support in test harness needs more work  (was: remote host support in test harness needs more work because of security manager changes)
    Description: 
With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
permissions need to be passed in derby_test.policy for the client.
There is no technical reason for the remote host support to be useprocess=false.
The readme needs to be updated.
Also, there are some other changes that have caused for database objects to be left behind, which is a problem because with remote host, databases are re-used.



  was:
With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
permissions need to be passed in derby_test.policy for the client.


> remote host support in test harness needs more work
> ---------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>  Attachments: DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.
> There is no technical reason for the remote host support to be useprocess=false.
> The readme needs to be updated.
> Also, there are some other changes that have caused for database objects to be left behind, which is a problem because with remote host, databases are re-used.

-- 
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-871) remote host support in test harness needs more work

Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-871?page=comments#action_12365334 ] 

Andrew McIntyre commented on DERBY-871:
---------------------------------------

These changes look very straightforward, and since the latest patch does not include the change to where the security manager is installed during setup that Dan was concerned about, I will commit this shortly unless someone else objects.

> remote host support in test harness needs more work
> ---------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>  Attachments: DERBY-871-020606.diff, DERBY-871-020606.stat, DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.
> There is no technical reason for the remote host support to be useprocess=false.
> The readme needs to be updated.
> Also, there are some other changes that have caused for database objects to be left behind, which is a problem because with remote host, databases are re-used.

-- 
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-871) remote host support in test harness needs more work because of security manager changes

Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-871?page=comments#action_12364424 ] 

Kathey Marsden commented on DERBY-871:
--------------------------------------


>
>1) How are the new properties csinfo.server and csinfo.client different to cs.serverhost and cs.trustedhost?
>
Looking at the patch I am guessing they are the same thing, but it was a lack of proper documentation in the policy file that led to the addition of the new properties.  Because the tests were only set up to run locally before myrna did the remote host work, I think the harness was always passing localhost before.

>2) Why is csinfo.trustedhost granted 'connect' permission for derbynet.jar in the testing policy file?
>The server isn't connectiing to the client is it?
>
I don't know.  It doesn't sound right.

>
>3) Would csinfo.clienthost be a better name for csinfo.trustedhost? 
>
I think so.  or better yet something with derby instead of cs. Not the world's best namer though.

>It's possible that the remote testing (even using useProcess=false) does not need any changes to the >policy file or the harness.

That would be cool, but please take a look at our other thread on this issue about the database creation.




> remote host support in test harness needs more work because of security manager changes
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>  Attachments: DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.

-- 
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-871) remote host support in test harness needs more work

Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-871?page=all ]

Myrna van Lunteren updated DERBY-871:
-------------------------------------

    Attachment: DERBY-871-020606.stat
                DERBY-871-020606.diff

The new patch, DERBY-871_020606.*, has 2 basic purposes:
- remove the need for useprocess false with remote server configuration
- fix up some tests so they can run in remote server configuration
contains the following changes:
M      java\drda\org\apache\derby\impl\drda\TestProto.java
              fixed up dependency on useprocess false directory structure with hostName != localhost.
M      java\testing\README.htm
            -  removed references to useprocess false in -DhostName section
            -  added more few comments to useprocess to explain impact better
            -  in passing fixed up path referene to multi tests as reported by someone on the list
            -  removed the 'last updated ' line - anyone updating the doc forgets
                  to do modify this  (incl. me), so really should rely on version control info for this.          
M      java\testing\org\apache\derbyTesting\functionTests\tests\lang\syscat_app.properties
                 make syscat create its own database. This way, the test may be run in remote host
                 configuration without relying on all other tests to be clean
M      java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\resultset.java
                 test was not properly cleaning up after itself
M      java\testing\org\apache\derbyTesting\functionTests\tests\derbynet\testSecMec.java
                 because of placing of InetAddres.getByName call, an additional socketPermission, "resolve" 
                 was needed for derbyTesting.jar in remote server configuration, for which I couldn't see
                 the point, as it is not a call specific to derby. 
M      java\testing\org\apache\derbyTesting\functionTests\tests\derbynet\prepStmt.java
                 test was not properly cleaning up after itself
M      java\testing\org\apache\derbyTesting\functionTests\harness\RunTest.java
                 remove useprocess=false when hostName != localhost
M      java\testing\org\apache\derbyTesting\functionTests\suites\DerbyNetRemote.exclude
M      java\testing\org\apache\derbyTesting\functionTests\suites\DerbyNetClientRemote.exclude
                adjust comments to no longer refer to useprocess, enable lang/syscat.sql

I ran derbyall, as well as derbynetmats and derbynetclientmats against a remote server, with insane jars.
There were no failures.

> remote host support in test harness needs more work
> ---------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>  Attachments: DERBY-871-020606.diff, DERBY-871-020606.stat, DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.
> There is no technical reason for the remote host support to be useprocess=false.
> The readme needs to be updated.
> Also, there are some other changes that have caused for database objects to be left behind, which is a problem because with remote host, databases are re-used.

-- 
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-871) remote host support in test harness needs more work because of security manager changes

Posted by "Myrna van Lunteren (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-871?page=all ]

Myrna van Lunteren updated DERBY-871:
-------------------------------------

    Other Info: [Patch available]

> remote host support in test harness needs more work because of security manager changes
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>  Attachments: DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.

-- 
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-871) remote host support in test harness needs more work because of security manager changes

Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-871?page=comments#action_12364389 ] 

Kathey Marsden commented on DERBY-871:
--------------------------------------

Hi Dan,

csinfo.serverhost   -  Host name or ip where network server is started. 
This is needed  for SocketPermission "accept"  for  NetworkServerControl andmin commands like  trace,  runtimeinfo  etc. These commands need to be executed  from the  host where network server was started.

csinfo.trustedhost   - Host name or ip from which client connections are allowed.

With regard to $csinfo.serverhost,  now that I think about it we could potentially use an alternate Socket constructor for these commands to bind the Socket to localhost, so that permission is not needed for the ip of  the host that started network server.  That way we could get rid of it all together (I think).

Speaking of naming,  properties etc,  as you have pointed out in the past, the test harness has a lot of properties that are tangled up with each other and not always clear.  Can you please offer your ideas on how to organize them for DERBY-817  to not aggravate that situation given the various dependencies and the fact that we will ultimately  want to move  away from the harness?


Thanks

Kathey



> remote host support in test harness needs more work because of security manager changes
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>  Attachments: DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.

-- 
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-871) remote host support in test harness needs more work because of security manager changes

Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-871?page=comments#action_12364384 ] 

Daniel John Debrunner commented on DERBY-871:
---------------------------------------------

In the policy file you've added two new properties, csinfo.client and csinfo.server but there are no comments in the top section indicating what those properties represent.

This coincides with a request I was going to make for someone to add comments to the policy file for the properties csinfo.serverhost and csinfo.trustedhost. That's part of the file I copied from nwsvr.policy but never understood.

Also, my question about the reason to run the tests differently should be answered before this patch is submitted.

> remote host support in test harness needs more work because of security manager changes
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>  Attachments: DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.

-- 
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-871) remote host support in test harness needs more work because of security manager changes

Posted by "Daniel John Debrunner (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-871?page=comments#action_12364386 ] 

Daniel John Debrunner commented on DERBY-871:
---------------------------------------------

In RunTest.java, what was the reason for changing the point at which the security manager is installed? I thought I had put it after the System.setIn/setOut calls so that the setIO permission was not required to be granted.

This file seems to have no real changes
java/testing/org/apache/derbyTesting/functionTests/suites/jdbc20.runall

These files seem to be unrelated to the bug
java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/resultset.java
java/testing/org/apache/derbyTesting/functionTests/tests/derbynet/prepStmt.java

> remote host support in test harness needs more work because of security manager changes
> ---------------------------------------------------------------------------------------
>
>          Key: DERBY-871
>          URL: http://issues.apache.org/jira/browse/DERBY-871
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.2.0.0
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>  Attachments: DERBY-874-012906.diff, DERBY-874-012906.stat
>
> With the changes to have security manager run for tests with useprocess=false, the remote host support in the test harness no l onger works.
> permissions need to be passed in derby_test.policy for the client.

-- 
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