db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "DerbyTenThreeRelease" by RichardHillegas
Date Thu, 07 Jun 2007 15:20:20 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by RichardHillegas:
http://wiki.apache.org/db-derby/DerbyTenThreeRelease

------------------------------------------------------------------------------
  || JIRA || really short description || owner || comments ||
  || Master JIRA: [https://issues.apache.org/jira/browse/DERBY-2264 DERBY-2264] || DBA Powers
|| Dag || recently escalated concerns re compatibility; see [https://issues.apache.org/jira/browse/DERBY-2728
DERBY-2728]. Also, pending doc fix, see [https://issues.apache.org/jira/browse/DERBY-2520
DERBY-2520]. ||
  || Master JIRA: [https://issues.apache.org/jira/browse/DERBY-1478 DERBY-1478] || Language
Based Ordering || Mamta || 4 sub issues are still open, including doc fix, see [https://issues.apache.org/jira/browse/DERBY-2337
DERBY-2337]. ||
- || Master JIRA: [https://issues.apache.org/jira/browse/DERBY-2757 DERBY-2757] || Secure
Server || Rick || recently escalated concerns re compatibility. Also, pending doc fix, see
[https://issues.apache.org/jira/browse/DERBY-2372 DERBY-2372]. ||
  
  possible, but not certain:
  [https://issues.apache.org/jira/browse/DERBY-2274 DERBY-2274],
@@ -91, +90 @@

  The Secure Server work ([https://issues.apache.org/jira/browse/DERBY-2196 DERBY-2196]) introduces
the following incompatibility during upgrade from an older Derby release:
  
  || '''Scenario''' || '''Old behavior''' || '''New behavior''' || '''Customer needs to make
these changes...''' ||
- ||  '''Unsecure with authentication'''|| In this scenario, !NetworkServerControl is the
main entry point for the VM and the VM starts up without a !SecurityManager. However, the
customer has set the system property derby.connection.requireAuthentication=true|| The server
comes up as before. However, under the hood,  !NetworkServerControl installs a !SecurityManager.
This may affect the running of customer-written procedures and functions. Application code
within routines will no longer be able to perform operations that require security checks
like file i/o, system-property-reading, classloading, etc.. || The customer does not need
to do anything if her routines are not perfoming such operations. If her routines are performing
such operations then there are (at least) two choices. 1) Bring the server up with the -noSecurityManager
flag if the !SecurityManager causes her problems--for instance, if she does not want to add
privileged blocks to her procedures and functions. 2)
  Bring the server up with her own security manager and policy file. ||
+ ||  '''Unsecure'''|| In this scenario, !NetworkServerControl is the main entry point for
the VM and the VM starts up without a !SecurityManager.|| The server comes up as before. However,
under the hood,  !NetworkServerControl installs a !SecurityManager. This may affect the running
of customer-written procedures and functions. Application code within routines will no longer
be able to perform operations that require security checks like file i/o, system-property-reading,
classloading, etc.. || The customer does not need to do anything if her routines are not perfoming
such operations. If her routines are performing such operations then there are (at least)
two choices. 1) Bring the server up with the -noSecurityManager flag if the !SecurityManager
causes her problems--for instance, if she does not want to add privileged blocks to her procedures
and functions. 2) Bring the server up with her own security manager and policy file. ||
- ||  '''Unsecure with no authentication'''|| In this scenario, !NetworkServerControl is the
main entry point for the VM and the VM starts up without a !SecurityManager. In addition,
the system property derby.connection.requireAuthentication is not set to true|| The server
fails to come up because user authentication is not turned on.|| The customer must either
turn on user authentication or bring the server up with the -noSecurityManager flag. ||
  
  
  The DBA Powers work ([https://issues.apache.org/jira/browse/DERBY-2264 DERBY-2264]) introduces
the following incompatibility during upgrade from an older Derby release:

Mime
View raw message