Return-Path: X-Original-To: apmail-db-general-archive@www.apache.org Delivered-To: apmail-db-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EA962E5AD for ; Fri, 28 Dec 2012 20:23:33 +0000 (UTC) Received: (qmail 26986 invoked by uid 500); 28 Dec 2012 20:23:33 -0000 Delivered-To: apmail-db-general-archive@db.apache.org Received: (qmail 26943 invoked by uid 500); 28 Dec 2012 20:23:33 -0000 Mailing-List: contact general-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: general@db.apache.org List-Id: Delivered-To: mailing list general@db.apache.org Received: (qmail 26936 invoked by uid 99); 28 Dec 2012 20:23:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Dec 2012 20:23:33 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Dec 2012 20:23:23 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id CEBD3238896F for ; Fri, 28 Dec 2012 20:23:00 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r844160 [1/2] - in /websites/production/db/content/derby/docs/10.8: adminguide/ devguide/ getstart/ ref/ tools/ tuning/ Date: Fri, 28 Dec 2012 20:22:57 -0000 To: general@db.apache.org From: kmarsden@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20121228202300.CEBD3238896F@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: kmarsden Date: Fri Dec 28 20:22:56 2012 New Revision: 844160 Log: DERBY-5924 Tasks for 10.8.3 maintenance release Update 10.8.3 docs. Also corrects some issues with non-ascii characters taht were showing up as ??. Only fixes that issue for 10.8. index.html and other versions still have the problem DERBY-6023 Modified: websites/production/db/content/derby/docs/10.8/adminguide/derbyadmin.pdf websites/production/db/content/derby/docs/10.8/devguide/cdevcollation.html websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts14433.html websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts19173.html websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts29416.html websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts838850.html websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts839085.html websites/production/db/content/derby/docs/10.8/devguide/cdevconceptssavepoints.html websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure24366.html websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure31493.html websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure60146.html websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure67151.html websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure866716.html websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure88690.html websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure96815.html websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure97760.html websites/production/db/content/derby/docs/10.8/devguide/cdevdvlp27715.html websites/production/db/content/derby/docs/10.8/devguide/cdevdvlp51654.html websites/production/db/content/derby/docs/10.8/devguide/derbydev.pdf websites/production/db/content/derby/docs/10.8/devguide/rdevdvlp847152.html websites/production/db/content/derby/docs/10.8/devguide/tdevconcepts839040.html websites/production/db/content/derby/docs/10.8/devguide/tdevcsecurenewbootpw.html websites/production/db/content/derby/docs/10.8/devguide/tdevcsecurenewextkey.html websites/production/db/content/derby/docs/10.8/devguide/tdevcsecurenewkeyoverview.html websites/production/db/content/derby/docs/10.8/devguide/tdevcsecureunencrypteddb.html websites/production/db/content/derby/docs/10.8/devguide/tdevdvlp39090.html websites/production/db/content/derby/docs/10.8/devguide/tdevdvlpcollation.html websites/production/db/content/derby/docs/10.8/devguide/toc.html websites/production/db/content/derby/docs/10.8/getstart/cgsusingtoolsutils.html websites/production/db/content/derby/docs/10.8/getstart/common.css websites/production/db/content/derby/docs/10.8/getstart/commonltr.css websites/production/db/content/derby/docs/10.8/getstart/commonrtl.css websites/production/db/content/derby/docs/10.8/getstart/cwwdactivities.html websites/production/db/content/derby/docs/10.8/getstart/getstartderby.pdf websites/production/db/content/derby/docs/10.8/getstart/rgsdocs10012.html websites/production/db/content/derby/docs/10.8/getstart/tgsrunningdblook.html websites/production/db/content/derby/docs/10.8/getstart/tgsrunningij.html websites/production/db/content/derby/docs/10.8/getstart/tgsrunningsysinfo.html websites/production/db/content/derby/docs/10.8/getstart/tgssetupverify.html websites/production/db/content/derby/docs/10.8/getstart/twwdactivity1.html websites/production/db/content/derby/docs/10.8/getstart/twwdactivity1_Setup.html websites/production/db/content/derby/docs/10.8/getstart/twwdactivity1_overview.html websites/production/db/content/derby/docs/10.8/ref/refderby.pdf websites/production/db/content/derby/docs/10.8/ref/rrefattrib15290.html websites/production/db/content/derby/docs/10.8/ref/rrefattrib24612.html websites/production/db/content/derby/docs/10.8/ref/rrefattrib42100.html websites/production/db/content/derby/docs/10.8/ref/rrefattrib60346.html websites/production/db/content/derby/docs/10.8/ref/rrefattrib88843.html websites/production/db/content/derby/docs/10.8/ref/rrefattribencryptkey.html websites/production/db/content/derby/docs/10.8/ref/rrefattribnewbootpw.html websites/production/db/content/derby/docs/10.8/ref/rrefattribnewencryptkey.html websites/production/db/content/derby/docs/10.8/ref/rrefbuiltchar.html websites/production/db/content/derby/docs/10.8/ref/rrefexcept71493.html websites/production/db/content/derby/docs/10.8/ref/rrefjdbc27734.html websites/production/db/content/derby/docs/10.8/ref/rrefproper40688.html websites/production/db/content/derby/docs/10.8/ref/rrefsqlj1083019.html websites/production/db/content/derby/docs/10.8/ref/toc.html websites/production/db/content/derby/docs/10.8/tools/derbytools.pdf websites/production/db/content/derby/docs/10.8/tools/rtoolsijcomref16653.html websites/production/db/content/derby/docs/10.8/tools/rtoolsijcomref30679.html websites/production/db/content/derby/docs/10.8/tools/rtoolsijcomref36618.html websites/production/db/content/derby/docs/10.8/tools/rtoolsijcomref37862.html websites/production/db/content/derby/docs/10.8/tuning/ctunoptimzoverride.html websites/production/db/content/derby/docs/10.8/tuning/tuningderby.pdf Modified: websites/production/db/content/derby/docs/10.8/adminguide/derbyadmin.pdf ============================================================================== Binary files - no diff available. Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevcollation.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevcollation.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevcollation.html Fri Dec 28 20:22:56 2012 @@ -204,10 +204,10 @@ FRUIT ORDER BY NAME returns:
    The collation set for the database also impacts comparison operators on character data types. For example, the statement SELECT * FROM FRUIT WHERE NAME > 'Banana' ORDER BY NAME returns: -

    ????????????UCS_BASIC collation???????????? Territory-based collation
    -????????????????????????????????Grape????????????????????????????????????????????????????????????????Grape
    -????????????????????????????????Pineapple???????????????????????????????????????????????????? orange
    -????????????????????????????????????????????????????????????????????????????????????????????????????????????????????Pineapple

    +

          UCS_BASIC collation       Territory-based collation
    +                Grape                                Grape
    +                Pineapple                           orange
    +                                                          Pineapple

    For information on creating case-insensitive databases, see Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts14433.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts14433.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts14433.html Fri Dec 28 20:22:56 2012 @@ -79,7 +79,7 @@ information.

    Related concepts
    - +
    Related tasks
    Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts19173.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts19173.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts19173.html Fri Dec 28 20:22:56 2012 @@ -79,7 +79,7 @@ A new connection to a Derby database is
  • Turning off auto-commit
    You can disable auto-commit with the Connection class's setAutoCommit method.
  • Explicitly closing Statements, ResultSets, and Connections
    -You should explicitly close Statements, ResultSets, and Connections when you no longer need them.
    • +You should explicitly close Statements, ResultSets, and Connections when you no longer need them, unless you declare them in a try-with-resources statement (available in JDK 7 and after).
  • Statement versus transaction runtime rollback
    When an SQL statement generates an exception, this exception results in a runtime rollback. A runtime rollback is a system-generated rollback of a statement or transaction by Derby, as opposed to an explicit rollback call from your application.
  • Using savepoints
    Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts29416.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts29416.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts29416.html Fri Dec 28 20:22:56 2012 @@ -199,7 +199,7 @@ isolation mode and table-level locking.<
    • Related concepts
    - + Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts838850.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts838850.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts838850.html Fri Dec 28 20:22:56 2012 @@ -79,7 +79,7 @@ whether or not these objects were create
    Related concepts
    - +
    Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts839085.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts839085.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevconcepts839085.html Fri Dec 28 20:22:56 2012 @@ -26,8 +26,8 @@ - - + + @@ -49,17 +49,51 @@ -

    You should explicitly close Statements, ResultSets, and Connections when -you no longer need them.

    +

    You should explicitly close Statements, +ResultSets, and Connections when +you no longer need them, unless you declare them in a +try-with-resources statement (available in JDK 7 and +after).

    Connections to Derby are resources external to an application, and the garbage collector will not close them automatically.

    -

    For example, close a Statement object using its close method; -close a Connection object using its close method. -If auto-commit is disabled, active transactions need to be explicitly committed -or rolled back before closing the connection

    +

    To close a Statement, +ResultSet, or Connection object +that is not declared in a try-with-resources statement, +use its close method. If auto-commit is disabled, you +must explicitly commit or roll back active transactions before you close the +connection.

    + +

    Statements, result sets, and connections extend +AutoCloseable in JDK 7 and after. If you declare a +connection in a try-with-resources statement and there +is an error that the code does not catch, the JRE will attempt to close the +connection automatically.

    + +

    Note that a transaction-severity or higher exception causes +Derby to abort an in-flight +transaction. But a statement-severity exception does NOT roll back the +transaction. Also note that +Derby throws an exception if +an attempt is made to close a connection with an in-flight transaction. Suppose +now that a Connection is declared in a +try-with-resources statement, a transaction is +in-flight, and an unhandled statement-severity error occurs inside the +try-with-resources block. In this situation, +Derby will raise a follow-on +exception as the JRE exits the try-with-resources block. (For details on +error severity levels, see the documentation of the +derby.stream.error.logSeverityLevel property in the +Derby Reference Manual.)

    + +

    It is therefore always best to catch errors inside the +try-with-resources block and to either roll back or +commit, as appropriate, to ensure that there is no pending transaction when +leaving the try-with-resources block. This action also +improves application portability, since DBMSs differ in their semantics when +trying to close a connection with a pending transaction.

    Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevconceptssavepoints.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevconceptssavepoints.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevconceptssavepoints.html Fri Dec 28 20:22:56 2012 @@ -119,7 +119,7 @@ savepoint).

    Related concepts
    - +
    Related tasks
    Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure24366.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure24366.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure24366.html Fri Dec 28 20:22:56 2012 @@ -30,8 +30,6 @@ - - @@ -72,7 +70,8 @@ number of ways, including transport over might not know how, or might not have the means, to properly protect the data.

    This data encryption feature provides the ability to store user data in -an encrypted form. The user who boots the database must provide a boot password.

    +an encrypted form. The user who boots the database must provide a boot password +or encryption key.

    Note: Jar files stored in the database are not encrypted.
    @@ -99,10 +98,6 @@ This section describes using encryption
    -
    Related tasks
    - - -
    Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure31493.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure31493.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure31493.html Fri Dec 28 20:22:56 2012 @@ -47,35 +47,33 @@

    You can specify an alternate provider when you create the database -with the encryptionProvider=providerName attribute.

    +with the encryptionProvider=providerName attribute.

    You must specify the full package and class name of the provider, and you must also add the libraries to the application's classpath.

    - -
    -- using the the provider library jce_jdk13-10b4.zip|
+
    -- using the the provider library bcprov-jdk15on-147.jar
 -- available from www.bouncycastle.org
 jdbc:derby:encryptedDB3;create=true;dataEncryption=true;
 bootPassword=clo760uds2caPe;
 encryptionProvider=org.bouncycastle.jce.provider.BouncyCastleProvider;
 encryptionAlgorithm=DES/CBC/NoPadding
 
--- using a provider
--- available from
--- http://jcewww.iaik.tu-graz.ac.at/download.html
+-- using a provider available from
+-- http://jce.iaik.tugraz.at/sic/Download
 jdbc:derby:encryptedDB3;create=true;dataEncryption=true;
 bootPassword=clo760uds2caPe;
-encryptionProvider=iaik.security.provider.IAIK;encryptionAlgorithm=
-DES/CBC/NoPadding
    
+encryptionProvider=iaik.security.provider.IAIK;
+encryptionAlgorithm=DES/CBC/NoPadding
    Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure60146.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure60146.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure60146.html Fri Dec 28 20:22:56 2012 @@ -26,8 +26,8 @@ - - + + @@ -49,18 +49,18 @@ -

    If you create an encrypted database using the bootPassword attribute, -you must specify the boot password to reboot the database. If you create an -encrypted database using the encryptionKey attribute, you must specify -the encryptionKey to reboot the database.

    +

    If you create an encrypted database using the bootPassword=key +attribute, you must specify the boot password to reboot the database. If you +create an encrypted database using the encryptionKey=key attribute, you +must specify the encryption key to reboot the database.

    Encrypted databases cannot be booted automatically along with all other system databases on system startup (see "derby.system.bootAll" in the -Derby Reference Manual). Instead, you boot encrypted -databases when you first connect to the database.

    +Derby Reference Manual). Instead, you boot an encrypted +database when you first connect to the database.

    -
    Booting a database with the bootPassword attribute
    +
    Booting a database with the bootPassword=key attribute
    To access an encrypted database called wombat that was created with the boot password clo760uds2caPe, use the following @@ -68,13 +68,14 @@ connection URL:
    jdbc:derby:wombat;bo
    -
    Booting a database with the encryptionKey attribute
    +
    Booting a database with the encryptionKey=key attribute
    To access an encrypted database called flintstone that -was created with the encryptionKey=c566bab9ee8b62a5ddb4d9229224c678 and -with the encryptionAlgorithm=AES/CBC/NoPadding, use the following -connection URL: 
    jdbc:derby:flintstone;encryptionAlgorithm=AES/CBC/NoPadding;
-encryptionKey=c566bab9ee8b62a5ddb4d9229224c678
    +was created with the attributes +encryptionKey=c566bab9ee8b62a5ddb4d9229224c678 and +encryptionAlgorithm=AES/CBC/NoPadding, use the following +connection URL: +
    jdbc:derby:flintstone;encryptionKey=c566bab9ee8b62a5ddb4d9229224c678
    @@ -109,13 +110,13 @@ after it has been booted, turn on user a
    Parent topic: Working with encryption
    Related concepts
    - - + +
    Related tasks
    - - + +
    Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure67151.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure67151.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure67151.html Fri Dec 28 20:22:56 2012 @@ -104,8 +104,8 @@ is not supported by the provider you hav an exception.

    To specify the AES encryption algorithm with a key length other than the -default of 128, specify the encryptionKeyLength attribute. For example, -you might specify the following connection attributes:

    +default of 128, specify the encryptionKeyLength=length attribute. For +example, you might specify the following connection attributes:

     jdbc:derby:encdbcbc_192;create=true;dataEncryption=true;
@@ -123,10 +123,10 @@ length using the default policy jar file
 
 

Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure866716.html
==============================================================================
--- websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure866716.html (original)
+++ websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure866716.html Fri Dec 28 20:22:56 2012
@@ -25,9 +25,9 @@
 
 
 
-
-
-
+
+
+
 
 
 
@@ -37,17 +37,18 @@
 
 
 
-Creating the boot password
+Creating a boot password
 
 
 
 
-
    Creating the boot password
    
+
    Creating a boot password
    
 
 
 
-
    When you encrypt a database you must also specify a boot password,
-which is an alpha-numeric string used to generate the encryption key.
    
+
    When you encrypt a database you usually specify a boot password,
+which is an alphanumeric string used to generate the encryption key. (You can
+also specify an encryption key directly.)
    
 
 
    The length of the encryption key depends on the algorithm used:
    
 
@@ -67,18 +68,19 @@ of bytes in the encryption key (56 bits=
 bytes). The minimum number of characters for the boot password allowed by Derby is eight.
    
 
 
    It is a good idea not to use words that would be easily guessed, such as
-a login name or simple words or numbers. A bootPassword, like any password,
-should be a mix of numbers and upper- and lowercase letters.
    
+a login name or simple words or numbers. A boot password, like any password,
+should be a mix of numbers and uppercase and lowercase letters.
    
 
 
    You turn on and configure encryption and specify the corresponding boot
 password on the connection URL for a database when you create it:
    
 
 
    jdbc:derby:encryptionDB1;create=true;dataEncryption=true;
-    bootPassword=clo760uds2caPe
    
+bootPassword=clo760uds2caPe
    -
    Note: If you lose the bootPassword and the database is not currently +
    Note: If you lose the boot password and the database is not currently booted, you will not be able to connect to the database anymore. (If you know -the current bootPassword, you can change it. See Encrypting databases with a new key.)
    +the current boot password, you can change it. See +Encrypting databases with a new key.)
    @@ -94,8 +96,8 @@ Derby supports the following encryption
    Parent topic: Working with encryption
    Related concepts
    - - + +
    Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure88690.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure88690.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure88690.html Fri Dec 28 20:22:56 2012 @@ -26,8 +26,8 @@ - - + + @@ -49,23 +49,40 @@ -

    You configure a Derby database -for encryption when you create the database by specifying the dataEncryption=true attribute -on the connection URL.

    - -

    The Java Runtime Environment (JRE) determines the default encryption provider, -as follows:

    +

    You configure a +Derby database for encryption +when you create the database by specifying attributes on the connection URL.

      -
    • For J2SE/J2EE 1.4 or higher, the JRE's provider is the default.
      • +
    • To enable encryption, use the dataEncryption=true attribute.
      • + +
    • To provide a key for the encryption, specify either the +bootPassword=key attribute or the encryptionKey=key +attribute.
      • -
    • If your environment for some reason does not include a provider, it must be specified.
      • -
    -

    You have the option of specifying an alternate encryption provider. The -default encryption algorithm is DES, but you have the option of specifying -an alternate algorithm as well. See Specifying an alternate encryption provider

    +

    The following connection URL specifies a boot password:

    + +
    jdbc:derby:encryptedDB;create=true;dataEncryption=true;
+bootPassword=DBpassword
    + +
    The following URL specifies an encryption key: +
    jdbc:derby:encryptedDB;create=true;dataEncryption=true;
+encryptionKey=6162636465666768
    +
    + +

    The default encryption algorithm is DES.

    + +

    You can specify an encryption provider and/or encryption algorithm +other than the defaults by using the encryptionProvider=providerName and +encryptionAlgorithm=algorithm attributes. See +Specifying an alternate encryption provider and +Specifying an alternate encryption algorithm for more +information.

    + +

    See the Derby Reference Manual for details on the +connection URL attributes.

    @@ -74,8 +91,8 @@ an alternate algorithm as well. See Parent topic: Working with encryption
    Related concepts
    - - + +
    Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure96815.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure96815.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure96815.html Fri Dec 28 20:22:56 2012 @@ -50,12 +50,22 @@

    Derby supports disk encryption and requires an encryption provider. An encryption provider -implements the Java cryptography concepts. The JRE for Java SE 1.4 and -higher includes Java Cryptographic Extensions (JCE, part of the +implements the Java cryptography concepts. The Java Runtime Environment (JRE) +for Java SE includes Java Cryptographic Extensions (JCE, part of the Java Cryptography Architecture) and one or more default encryption providers. For more information, see the Java Cryptography Architecture (JCA) Reference Guide.

    +

    The JRE determines the default encryption provider as follows:

    + +
      +
    • The JRE's provider is the default.
      • + +
    • If your environment for some reason does not include a provider, it must be +specified.
      • + +
    + Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure97760.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure97760.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevcsecure97760.html Fri Dec 28 20:22:56 2012 @@ -56,15 +56,15 @@
    • Encrypting databases on creation
      -You configure a Derby database for encryption when you create the database by specifying the dataEncryption=true attribute on the connection URL.
      • +You configure a Derby database for encryption when you create the database by specifying attributes on the connection URL.
    • Encrypting an existing unencrypted database
      You can encrypt an unencrypted Derby database by specifying attributes on the connection URL when you boot the database. The attributes that you specify depend on how you want the database encrypted.
      • -
    • Creating the boot password
      -When you encrypt a database you must also specify a boot password, which is an alpha-numeric string used to generate the encryption key.
      • +
    • Creating a boot password
      +When you encrypt a database you usually specify a boot password, which is an alphanumeric string used to generate the encryption key. (You can also specify an encryption key directly.)
    • Encrypting databases with a new key
      You can apply a new encryption key to a Derby database by specifying a new boot password or a new external key.
    • Booting an encrypted database
      -If you create an encrypted database using the bootPassword attribute, you must specify the boot password to reboot the database. If you create an encrypted database using the encryptionKey attribute, you must specify the encryptionKey to reboot the database.
      • +If you create an encrypted database using the bootPassword=key attribute, you must specify the boot password to reboot the database. If you create an encrypted database using the encryptionKey=key attribute, you must specify the encryption key to reboot the database.
    Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevdvlp27715.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevdvlp27715.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevdvlp27715.html Fri Dec 28 20:22:56 2012 @@ -84,6 +84,9 @@ Loaded from file:C:\db-derby-10.7.1.0-bi java.vendor=Sun Microsystems Inc. java.runtime.version=1.6.0_24-b07 user.dir=C:\ +os.name=Windows XP +os.arch=x86 +os.version=5.1 derby.system.home=null Database Class Loader started - derby.database.classpath='' Modified: websites/production/db/content/derby/docs/10.8/devguide/cdevdvlp51654.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/cdevdvlp51654.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/cdevdvlp51654.html Fri Dec 28 20:22:56 2012 @@ -41,9 +41,6 @@ - - - @@ -72,6 +69,20 @@ obtaining a connection; see For more information on working with connection URL attributes, see the +following: +
      +
    • Encrypting databases on disk for information +on database encryption
      • + +
    • Derby Server and Administration Guide for information on tracing +network clients, replicating databases, restoring databases from backup, and +logging on separate devices
      • + +
    + +
    +

    For complete information about the attributes, see "Setting attributes for the database connection URL" in the Derby Reference Manual.

    @@ -93,12 +104,6 @@ You create a database by supplying a new When user authentication is enabled, an application must provide a user name and password. One way to do this is to use the user=userName and password=userPassword connection URL attributes.
  • Creating a database with territory-based collation
    By default, Derby uses Unicode codepoint collation. However, you can specify territory-based collation when you create the database.
    • -
  • Encrypting a database when you create it
    -If your environment is configured properly, you can create your database as an encrypted database (one in which the database is encrypted on disk). To do this, you use the dataEncryption=true attribute to turn on encryption and the bootPassword=key attribute or the encryptionKey attribute to specify a key for the encryption.
    • -
  • Creating an encrypted database with an external key
    -You can create a database and encrypt the database with an external key.
    • -
  • Booting an encrypted database
    -You must specify several attributes in the URL when you boot an encrypted database. You must specify these attributes the first time that you connect to the database within a JVM session, or after you shut the database down within the same JVM session.
  • Specifying attributes in a properties object
    Instead of specifying attributes on the connection URL, you can specify attributes as properties in a Properties object that you pass as a second argument to the DriverManager.getConnection method.
Modified: websites/production/db/content/derby/docs/10.8/devguide/derbydev.pdf ============================================================================== Binary files - no diff available. Modified: websites/production/db/content/derby/docs/10.8/devguide/rdevdvlp847152.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/rdevdvlp847152.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/rdevdvlp847152.html Fri Dec 28 20:22:56 2012 @@ -33,8 +33,6 @@ - - @@ -80,8 +78,6 @@ like this:

- - Modified: websites/production/db/content/derby/docs/10.8/devguide/tdevconcepts839040.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/tdevconcepts839040.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/tdevconcepts839040.html Fri Dec 28 20:22:56 2012 @@ -63,7 +63,7 @@
Related concepts
- +
Modified: websites/production/db/content/derby/docs/10.8/devguide/tdevcsecurenewbootpw.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/tdevcsecurenewbootpw.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/tdevcsecurenewbootpw.html Fri Dec 28 20:22:56 2012 @@ -26,8 +26,8 @@ - - + + @@ -49,27 +49,27 @@

You can apply a new boot password to a Derby database -by specifying the newBootPassword attribute on the connection URL when -you boot the database.

+by specifying the newBootPassword=newPassword attribute on the connection +URL when you boot the database.

  • If the database is configured with log archival for roll-forward recovery, you must disable log archival and perform a shutdown before you can encrypt the database with a new boot password.
    • -
  • If there are any global transaction that are in the prepared state after +
  • If any global transactions are in the prepared state after recovery, the database cannot be encrypted with a new boot password.
  • If the database is currently encrypted with an external encryption key, -you should use the newEncryptionKey attribute -to encrypt the database.
    • +use the +newEncryptionKey=key attribute to encrypt the database.
-

When you use the newBootPassword attribute, a new encryption -key is generated internally by the engine and the key is protected using the -new boot password. The newly generated encryption key encrypts the database, +

When you use the newBootPassword=newPassword attribute, a new +encryption key is generated internally by the engine, and the key is protected +using the new boot password. The newly generated encryption key encrypts the database, including the existing data. You cannot change the encryption provider or encryption algorithm when you apply a new boot password.

To encrypt @@ -77,10 +77,13 @@ a database with a new boot password:

-
Specify the newBootPassword attribute in a URL and reboot -the database. For example, when the following URL is used when -the salesdb database is rebooted, the database is encrypted -with the new encryption key, and is protected by the password new1234xyz:
 jdbc:derby:salesdb;bootPassword=abc1234xyz;newBootPassword=new1234xyz
+
Specify the newBootPassword=newPassword attribute in a URL and +reboot the database. + For example, if you use the following URL to reboot +the salesdb database, the database is encrypted +with the new encryption key and is protected by the password +new1234xyz: +
jdbc:derby:salesdb;bootPassword=abc1234xyz;newBootPassword=new1234xyz

@@ -108,11 +111,11 @@ particularly "Roll-forward recovery".

Parent topic: Encrypting databases with a new key
Related concepts
- +
Related tasks
- +
Modified: websites/production/db/content/derby/docs/10.8/devguide/tdevcsecurenewextkey.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/tdevcsecurenewextkey.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/tdevcsecurenewextkey.html Fri Dec 28 20:22:56 2012 @@ -26,8 +26,8 @@ - - + + @@ -49,7 +49,7 @@

You can apply a new external encryption key to a Derby database -by specifying the newEncryptionKey attribute on the connection URL +by specifying the newEncryptionKey=key attribute on the connection URL when you boot the database.

    @@ -57,12 +57,13 @@ when you boot the database.

    you must disable log archival and perform a shutdown before you can encrypt the database with a new external encryption key. -
  • If there are any global transaction that are in the prepared state after +
  • If any global transaction are in the prepared state after recovery, the database cannot be encrypted with a new encryption key.
    • -
  • If the database is currently encrypted with a boot password , you should -use the newBootPassword attribute -to encrypt the database.
    • +
  • If the database is currently encrypted with a boot password, +use the +newBootPassword=newPassword attribute to encrypt the +database.
@@ -71,10 +72,13 @@ to encrypt the database.
-
Specify the newEncryptionKey attribute in a URL and reboot -the database. For example, when the following URL is used when -the salesdb database is rebooted, the database is encrypted -with the new encryption key 6862636465666768:
jdbc:derby:salesdb;encryptionKey=6162636465666768;newEncryptionKey=6862636465666768'
+
Specify the newEncryptionKey=key attribute in a URL and reboot +the database. For example, if you use the following URL to reboot +the salesdb database, the database is encrypted +with the new encryption key 6862636465666768: +
jdbc:derby:salesdb;encryptionKey=6162636465666768;
+newEncryptionKey=6862636465666768'
+

@@ -102,11 +106,11 @@ particularly "Roll-forward recovery".

Parent topic: Encrypting databases with a new key
Related concepts
- +
Related tasks
- +
Modified: websites/production/db/content/derby/docs/10.8/devguide/tdevcsecurenewkeyoverview.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/tdevcsecurenewkeyoverview.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/tdevcsecurenewkeyoverview.html Fri Dec 28 20:22:56 2012 @@ -50,10 +50,10 @@

You can apply a new encryption key to a Derby database by specifying a new boot password or a new external key.

-

Encrypting a database with a new encryption key is a time consuming +

Encrypting a database with a new encryption key is a time-consuming process because it involves encrypting all of the existing data in the database with the new encryption key. If the process is interrupted before completion, -all the changes are rolled back the next time that the database is booted. +all the changes are rolled back the next time the database is booted. If the interruption occurs immediately after the database is encrypted with the new encryption key but before the connection is returned to the application, you might not be able to boot the database with the old encryption key. In @@ -63,7 +63,7 @@ encryption key.

you have enough free disk space before you encrypt a database with a new key. In addition to the disk space required for the current size of the database, temporary disk space is required to store the old version of the data to restore -the database back to it's original state if the new encryption is interrupted +the database back to its original state if the new encryption is interrupted or returns errors. All of the temporary disk space is released back to the operating system after the database is reconfigured to work with the new encryption key.
@@ -75,10 +75,12 @@ key.
database: @@ -101,7 +103,7 @@ the database with a new external encrypt
Parent topic: Working with encryption
Related concepts
- +
Related tasks
Modified: websites/production/db/content/derby/docs/10.8/devguide/tdevcsecureunencrypteddb.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/tdevcsecureunencrypteddb.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/tdevcsecureunencrypteddb.html Fri Dec 28 20:22:56 2012 @@ -55,22 +55,29 @@ The attributes that you specify depend o
  • If the database is configured with log archival, you must disable log archival and perform a shutdown before you can encrypt the database.
    • -
  • If there are any global transaction that are in the prepared state after +
  • If any global transactions are in the prepared state after recovery, the database cannot be encrypted.

    • When you encrypt an existing, unencrypted database, you can specify -whether the database should be encrypted using a boot password or an external -encryption key. You can also specify the encryptionProvider attribute -and the encryptionAlgorithm attribute on the connection URL. The database -is configure with the specified encryption attributes and all of the existing -data in the database is encrypted.

    -

    Encrypting a database is a time -consuming process because it involves encrypting all of the existing data +whether the database should be encrypted using a boot password +(bootPassword=key) or an external encryption key +(encryptionKey=key). You can also specify the +encryptionProvider=providerName attribute and the +encryptionAlgorithm=algorithm attribute on the connection URL. The +database +is configured with the specified encryption attributes, and all of the existing +data in the database is encrypted.

    + +

    See the Derby Reference Manual for details on the +connection URL attributes.

    + +

    Encrypting a database is a +time-consuming process because it involves encrypting all of the existing data in the database. If the process is interrupted before completion, all the -changes are rolled back the next time that the database is booted. If the +changes are rolled back the next time the database is booted. If the interruption occurs immediately after the database is encrypted but before the connection is returned to the application, you might not be able to boot the database without the boot password or external encryption key. In these @@ -80,7 +87,7 @@ or the external encryption key.

    that you have enough free disk space before you encrypt a database. In addition to the disk space required for the current size of the database, temporary disk space is required to store the old version of the data to restore the -database back to it's original state if the encryption is interrupted or returns +database back to its original state if the encryption is interrupted or returns errors. All of the temporary disk space is released back to the operating system after the database is encrypted.

    To encrypt an existing unencrypted @@ -88,8 +95,9 @@ database:

    -
    Specify the dataEncryption=true attribute and either the encryptionKey attribute -or the bootPassword attribute in a URL and boot the database. +
    Specify the dataEncryption=true attribute and either the +encryptionKey=key attribute or the bootPassword=key attribute in +a connection URL and boot the database. For example, to encrypt the salesdb database with the boot password abc1234xyz, specify the following attributes in the URL:
    jdbc:derby:salesdb;dataEncryption=true;bootPassword=abc1234xyz
    @@ -121,7 +129,7 @@ recovery".

    Parent topic: Working with encryption
    Related concepts
    - +
    Related tasks
    Modified: websites/production/db/content/derby/docs/10.8/devguide/tdevdvlp39090.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/tdevdvlp39090.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/tdevdvlp39090.html Fri Dec 28 20:22:56 2012 @@ -32,8 +32,6 @@ - - @@ -70,8 +68,6 @@ more details about create=true,
    Related tasks
    - -
    Related reference
    Modified: websites/production/db/content/derby/docs/10.8/devguide/tdevdvlpcollation.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/tdevdvlpcollation.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/tdevdvlpcollation.html Fri Dec 28 20:22:56 2012 @@ -79,7 +79,7 @@ TERRITORY_BASED with a colon to separate 
    jdbc:derby:SwedishDB;create=true;territory=sv_SE;collation=TERRITORY_BASED:PRIMARY

    With strength PRIMARY, the characters 'A' and 'a' will be considered equal, -as well as '??' ('a' with a grave accent). (This behavior is +as well as 'à' ('a' with a grave accent). (This behavior is commonly the default with many other databases.) To make searches respect differences in accent, use strength SECONDARY.

    Modified: websites/production/db/content/derby/docs/10.8/devguide/toc.html ============================================================================== --- websites/production/db/content/derby/docs/10.8/devguide/toc.html (original) +++ websites/production/db/content/derby/docs/10.8/devguide/toc.html Fri Dec 28 20:22:56 2012 @@ -108,9 +108,6 @@
  • Creating and accessing a database
  • Providing a user name and password
  • Creating a database with territory-based collation
    • -
  • Encrypting a database when you create it
    • -
  • Creating an encrypted database with an external key
    • -
  • Booting an encrypted database
  • Specifying attributes in a properties object
    • @@ -444,7 +441,7 @@