[jira] Commented: (DERBY-42) When using encryption, do not store the length information about the external key in service.properties

The following comment has been added to this issue:

     Author: Daniel John Debrunner
    Created: Fri, 15 Oct 2004 7:49 AM
       Body:
Also can the property derby.encryptionBlockSize be removed from the 
service.properties file when an external key is used.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/DERBY-42?page=comments#action_54197

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/DERBY-42

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: DERBY-42
    Summary: When using encryption, do not store the length information about 
the external key in service.properties
       Type: Improvement

     Status: Open
   Priority: Major

    Project: Derby
 Components: 
             Services
   Fix Fors:
             10.0.2.0
   Versions:
             10.0.2.0

   Assignee: Sunitha Kambhampati
   Reporter: Sunitha Kambhampati

    Created: Thu, 14 Oct 2004 5:26 PM
    Updated: Fri, 15 Oct 2004 7:49 AM
Environment: all

Description:
When using derby database encryption,there is a provision to provide the key to 
be used for encryption as an external key. In this case the key is not stored 
in the database for added security.  

There should not be any useful information about the external key that was used 
for encrypting the database in the service.properties.
Right now, key length is stored in service.properties. This should not be 
stored in service.properties.




---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira