[ 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
