db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rhille...@apache.org
Subject svn commit: r448934 - /db/derby/code/branches/10.2/RELEASE-NOTES.html
Date Fri, 22 Sep 2006 13:57:51 GMT
Author: rhillegas
Date: Fri Sep 22 06:57:50 2006
New Revision: 448934

URL: http://svn.apache.org/viewvc?view=rev&rev=448934
DERBY-1860: Update release notes: 1) Add note for DERBY-1867, 2) Refer the user to the wiki
for instructions on how to build jdbc4 support.


Modified: db/derby/code/branches/10.2/RELEASE-NOTES.html
URL: http://svn.apache.org/viewvc/db/derby/code/branches/10.2/RELEASE-NOTES.html?view=diff&rev=448934&r1=448933&r2=448934
--- db/derby/code/branches/10.2/RELEASE-NOTES.html (original)
+++ db/derby/code/branches/10.2/RELEASE-NOTES.html Fri Sep 22 06:57:50 2006
@@ -46,9 +46,6 @@
  <li>Secure connections can now be required. See
  <a href="http://issues.apache.org/jira/browse/DERBY-928">DERBY-928</a>.
- <li>Where possible, userids and passwords are encrypted. See
- <a href="http://issues.apache.org/jira/browse/DERBY-962">DERBY-962</a>.
- </li>
  <li>Support has been added for DRDA userid/password substitution. See
  <a href="http://issues.apache.org/jira/browse/DERBY-528">DERBY-528</a>.
@@ -179,20 +176,14 @@
-You may build this optional JDBC 4.0 support as follows. (See also
-<a href="http://issues.apache.org/jira/browse/DERBY-1846">DERBY-1846</a>)
+To build this optional JDBC 4.0 support yourself,
+please download the source
+distribution and consult BUILDING.txt.
+You may also follow a simplified set of instructions for building JDBC
+4.0 support, which you may find on the
+<a href="http://wiki.apache.org/db-derby/">Derby wiki</a>.
-<li>Download the -bin and -src distributions of Derby and unzip them.</li>
-<li>Set the environment variable DERBY_HOME in your shell environment to the location
where you have unzipped the -bin distribution.</li>
-<li>Set the environment variable JAVA_HOME in your shell environment to the location
of a JDK 1.6 JVM.</li>
-<li>In your shell, change directory into the tools/jdbc4 directory where you unzipped
the -src distribution.</li>
-<li>Run the update-with-jdbc4 script (or batch file on Windows), and the
-jars in $DERBY_HOME/lib will be updated with the necessary JDBC 4
-support classes.</li>
 <h2><a name="New Features"></a>New Features</h2>
@@ -281,10 +272,6 @@
        <TD><a href="http://issues.apache.org/jira/browse/DERBY-928">DERBY-928</a></TD>
        <TD>Restrict client connections,derby.drda.securityMechanism</TD>    
-       <TD><a href="http://issues.apache.org/jira/browse/DERBY-962">DERBY-962</a></TD>
-       <TD>Encrypt userid/password where possible</TD>
-     </TR>
-     <TR>
        <TD><a href="http://issues.apache.org/jira/browse/DERBY-1019">DERBY-1019</a></TD>
        <TD>Simplify tool invocation</TD>
@@ -976,6 +963,7 @@
 <li><a href="#1384">1384</a> - Increase default BLOB/CLOB length to maximum
supported (2G?)</li>
 <li><a href="#1621">1621</a> - Trigger action statement is not recompile
when there is a change that would affect it.</li>
 <li><a href="#1652">1652</a> - Update trigger updating the same rows as
the original update does not throw an exception ERROR 54038: "Maximum depth of nested triggers
was exceeded" as it should</li>
+<li><a href="#1867">1867</a> - Document algorithm support required for
using secmec 8(USRSSSBPWD) and limitation on ibm141 vm.</li>
@@ -1828,6 +1816,51 @@
 In the above statement, the trigger will only fire when an update
 is made to the "info" column instead of any column(s). 
+<a name="1867"></a>
+<a href="http://issues.apache.org/jira/browse/DERBY-1867">DERBY-1867</a>
+With IBM 1.4.1 JVM, trying to connect to the server using the derby client with security
mechanism 8 (USRSSSBPWD) will result in error.
+Connecting using the client driver with security mechanism 8 will throw the following error
+ERROR XJ112: Security exception encountered, see next exception for details.
+The stack trace will show that the problem is caused by java.security.NoSuchAlgorithmException:
SHA1PRNG SecureRandom not available
+Current USRSSBPWD implementation uses SHA1PRNG algorithm to generate random number(seed)
that gets exchanged between client and the server. The SHA1PRNG algorithm is not available
with the JCE provider that comes with IBM JVM version 1.4.1.
+You must use another JCE provider.
+If you need to use the security mechanism 8, then make sure that support for SHA1PRNG is
available in the JCE provider that is available with a particular JVM.
+For e.g. Use IBM 1.4.2 JVM that has support for SHA1PRNG or the Sun JVMs.

View raw message