[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang updated GERONIMO-4296: Attachment: pom.xml GERONIMO-4296-branch-21.patch The patch for branch 2.1 is ready, please help to review and follow the steps below to commit it. 1. apply patch GERONIMO-4296-branch-xy.patch 2. create folder plugins\derby\derby 3. move all files under plugins\derby\ to plugin\derby\derby 4. add pom.xml into plugins\derby\ 5. move plugins\system-database\geronimo-derby to plugins\derby\geronimo-derby Janet > Start Derby NetworkServerControl with credentials to prevent unauthorized > shutdowns > --- > > Key: GERONIMO-4296 > URL: https://issues.apache.org/jira/browse/GERONIMO-4296 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.0.3, 2.1.3, 2.1.4, 2.2 >Reporter: Donald Woods >Assignee: Donald Woods >Priority: Minor > Fix For: Wish List > > Attachments: GERONIMO-4296-branch-21.patch, pom.xml > > > Use the new NetworkServerControl support in Derby 10.4.1.3 and later to start > our embedded Derby server with credentials, to prevent any other apps on > localhost from stopping our Derby instance. The following Derby release note > details the scenario and the new API - > http://db.apache.org/derby/releases/release-10.4.1.3.html#Note+for+DERBY-3585 > We could either use random uid/pwd values to start the Derby server, which > would be the most secure, but would keep other apps from using our Derby > server. The other option, would be to set uid/pwd GBean attributes and > default the to the default system/manager values and leave it up to the user > to change them. > Note: This may also require some Samples, Testsuite and Portlet chagnes to > handle the required DB auth. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang updated GERONIMO-4296: Attachment: G4296-Patch-branch-21.zip G4296-Patch-branch-22.zip I create a patch for branch 22 (G4296-Patch-branch-22.zip). I also notice that a new change required for branch 21, so I re-create the patch for branch 21 (G4296-Patch-branch-21.zip). Please ignore the previous attachments, and use the files in zip for branch 21. Janet > Start Derby NetworkServerControl with credentials to prevent unauthorized > shutdowns > --- > > Key: GERONIMO-4296 > URL: https://issues.apache.org/jira/browse/GERONIMO-4296 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.0.3, 2.1.3, 2.1.4, 2.2 >Reporter: Donald Woods >Assignee: Donald Woods >Priority: Minor > Fix For: Wish List > > Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip, > GERONIMO-4296-branch-21.patch, pom.xml > > > Use the new NetworkServerControl support in Derby 10.4.1.3 and later to start > our embedded Derby server with credentials, to prevent any other apps on > localhost from stopping our Derby instance. The following Derby release note > details the scenario and the new API - > http://db.apache.org/derby/releases/release-10.4.1.3.html#Note+for+DERBY-3585 > We could either use random uid/pwd values to start the Derby server, which > would be the most secure, but would keep other apps from using our Derby > server. The other option, would be to set uid/pwd GBean attributes and > default the to the default system/manager values and leave it up to the user > to change them. > Note: This may also require some Samples, Testsuite and Portlet chagnes to > handle the required DB auth. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang updated GERONIMO-4296: Attachment: (was: pom.xml) > Start Derby NetworkServerControl with credentials to prevent unauthorized > shutdowns > --- > > Key: GERONIMO-4296 > URL: https://issues.apache.org/jira/browse/GERONIMO-4296 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.0.3, 2.1.3, 2.1.4, 2.2 >Reporter: Donald Woods >Assignee: Donald Woods >Priority: Minor > Fix For: Wish List > > Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip > > > Use the new NetworkServerControl support in Derby 10.4.1.3 and later to start > our embedded Derby server with credentials, to prevent any other apps on > localhost from stopping our Derby instance. The following Derby release note > details the scenario and the new API - > http://db.apache.org/derby/releases/release-10.4.1.3.html#Note+for+DERBY-3585 > We could either use random uid/pwd values to start the Derby server, which > would be the most secure, but would keep other apps from using our Derby > server. The other option, would be to set uid/pwd GBean attributes and > default the to the default system/manager values and leave it up to the user > to change them. > Note: This may also require some Samples, Testsuite and Portlet chagnes to > handle the required DB auth. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Han Hong Fang updated GERONIMO-4296: Attachment: (was: GERONIMO-4296-branch-21.patch) > Start Derby NetworkServerControl with credentials to prevent unauthorized > shutdowns > --- > > Key: GERONIMO-4296 > URL: https://issues.apache.org/jira/browse/GERONIMO-4296 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.0.3, 2.1.3, 2.1.4, 2.2 >Reporter: Donald Woods >Assignee: Donald Woods >Priority: Minor > Fix For: Wish List > > Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip > > > Use the new NetworkServerControl support in Derby 10.4.1.3 and later to start > our embedded Derby server with credentials, to prevent any other apps on > localhost from stopping our Derby instance. The following Derby release note > details the scenario and the new API - > http://db.apache.org/derby/releases/release-10.4.1.3.html#Note+for+DERBY-3585 > We could either use random uid/pwd values to start the Derby server, which > would be the most secure, but would keep other apps from using our Derby > server. The other option, would be to set uid/pwd GBean attributes and > default the to the default system/manager values and leave it up to the user > to change them. > Note: This may also require some Samples, Testsuite and Portlet chagnes to > handle the required DB auth. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-4296: --- Assignee: (was: Donald Woods) > Start Derby NetworkServerControl with credentials to prevent unauthorized > shutdowns > --- > > Key: GERONIMO-4296 > URL: https://issues.apache.org/jira/browse/GERONIMO-4296 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.0.3, 2.1.3, 2.1.4, 2.2 >Reporter: Donald Woods >Priority: Minor > Fix For: Wish List > > Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip > > > Use the new NetworkServerControl support in Derby 10.4.1.3 and later to start > our embedded Derby server with credentials, to prevent any other apps on > localhost from stopping our Derby instance. The following Derby release note > details the scenario and the new API - > http://db.apache.org/derby/releases/release-10.4.1.3.html#Note+for+DERBY-3585 > We could either use random uid/pwd values to start the Derby server, which > would be the most secure, but would keep other apps from using our Derby > server. The other option, would be to set uid/pwd GBean attributes and > default the to the default system/manager values and leave it up to the user > to change them. > Note: This may also require some Samples, Testsuite and Portlet chagnes to > handle the required DB auth. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang updated GERONIMO-4296: -- Fix Version/s: 2.1.6 2.2.1 (was: Wish List) > Start Derby NetworkServerControl with credentials to prevent unauthorized > shutdowns > --- > > Key: GERONIMO-4296 > URL: https://issues.apache.org/jira/browse/GERONIMO-4296 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.0.3, 2.1.3, 2.1.4, 2.2 >Reporter: Donald Woods >Priority: Minor > Fix For: 2.1.6, 2.2.1 > > Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip > > > Use the new NetworkServerControl support in Derby 10.4.1.3 and later to start > our embedded Derby server with credentials, to prevent any other apps on > localhost from stopping our Derby instance. The following Derby release note > details the scenario and the new API - > http://db.apache.org/derby/releases/release-10.4.1.3.html#Note+for+DERBY-3585 > We could either use random uid/pwd values to start the Derby server, which > would be the most secure, but would keep other apps from using our Derby > server. The other option, would be to set uid/pwd GBean attributes and > default the to the default system/manager values and leave it up to the user > to change them. > Note: This may also require some Samples, Testsuite and Portlet chagnes to > handle the required DB auth. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang updated GERONIMO-4296: -- Fix Version/s: 2.2.2 (was: 2.2.1) won't fix this in 221 release. > Start Derby NetworkServerControl with credentials to prevent unauthorized > shutdowns > --- > > Key: GERONIMO-4296 > URL: https://issues.apache.org/jira/browse/GERONIMO-4296 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.0.3, 2.1.3, 2.1.4, 2.2 >Reporter: Donald Woods >Assignee: Ivan >Priority: Minor > Fix For: 2.1.6, 2.2.2 > > Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip > > > Use the new NetworkServerControl support in Derby 10.4.1.3 and later to start > our embedded Derby server with credentials, to prevent any other apps on > localhost from stopping our Derby instance. The following Derby release note > details the scenario and the new API - > http://db.apache.org/derby/releases/release-10.4.1.3.html#Note+for+DERBY-3585 > We could either use random uid/pwd values to start the Derby server, which > would be the most secure, but would keep other apps from using our Derby > server. The other option, would be to set uid/pwd GBean attributes and > default the to the default system/manager values and leave it up to the user > to change them. > Note: This may also require some Samples, Testsuite and Portlet chagnes to > handle the required DB auth. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire updated GERONIMO-4296: --- Fix Version/s: 2.1.7 (was: 2.1.6) > Start Derby NetworkServerControl with credentials to prevent unauthorized > shutdowns > --- > > Key: GERONIMO-4296 > URL: https://issues.apache.org/jira/browse/GERONIMO-4296 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.0.3, 2.1.3, 2.1.4, 2.2 >Reporter: Donald Woods >Assignee: Ivan >Priority: Minor > Fix For: 2.1.7, 2.2.2 > > Attachments: G4296-Patch-branch-21.zip, G4296-Patch-branch-22.zip > > > Use the new NetworkServerControl support in Derby 10.4.1.3 and later to start > our embedded Derby server with credentials, to prevent any other apps on > localhost from stopping our Derby instance. The following Derby release note > details the scenario and the new API - > http://db.apache.org/derby/releases/release-10.4.1.3.html#Note+for+DERBY-3585 > We could either use random uid/pwd values to start the Derby server, which > would be the most secure, but would keep other apps from using our Derby > server. The other option, would be to set uid/pwd GBean attributes and > default the to the default system/manager values and leave it up to the user > to change them. > Note: This may also require some Samples, Testsuite and Portlet chagnes to > handle the required DB auth. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4296) Start Derby NetworkServerControl with credentials to prevent unauthorized shutdowns
[ https://issues.apache.org/jira/browse/GERONIMO-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks updated GERONIMO-4296: --- Fix Version/s: (was: 2.2) Wish List Good idea but lacks implementation > Start Derby NetworkServerControl with credentials to prevent unauthorized > shutdowns > --- > > Key: GERONIMO-4296 > URL: https://issues.apache.org/jira/browse/GERONIMO-4296 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.0.3, 2.1.3, 2.1.4, 2.2 >Reporter: Donald Woods >Assignee: Donald Woods >Priority: Minor > Fix For: Wish List > > > Use the new NetworkServerControl support in Derby 10.4.1.3 and later to start > our embedded Derby server with credentials, to prevent any other apps on > localhost from stopping our Derby instance. The following Derby release note > details the scenario and the new API - > http://db.apache.org/derby/releases/release-10.4.1.3.html#Note+for+DERBY-3585 > We could either use random uid/pwd values to start the Derby server, which > would be the most secure, but would keep other apps from using our Derby > server. The other option, would be to set uid/pwd GBean attributes and > default the to the default system/manager values and leave it up to the user > to change them. > Note: This may also require some Samples, Testsuite and Portlet chagnes to > handle the required DB auth. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
