db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1373) Encrypted databases cannot be booted using the jar subprotocol (and possibly also using http/https/classpath)
Date Fri, 21 Jul 2006 16:54:15 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1373?page=all ]

Sunitha Kambhampati updated DERBY-1373:

    Attachment: 10.1_derby1373.diff.txt

I  would like this fix to go into 10.1 branch. 

The below merge command to put this fix to 10.1 does not apply cleanly because of conflict
in encryptionAll.runall
svn merge -r 423681:423682 https://svn.apache.org/repos/asf/db/derby/code/trunk/

So, I am attaching a patch 10.1_derby1373.diff.txt for 10.1 codeline. Please note, it is the
same changes as derby1373.diff.txt.

svn stat:
M      java\engine\org\apache\derby\impl\services\jce\JCECipherFactory.java
M      java\testing\org\apache\derbyTesting\functionTests\tests\store\copyfiles.ant
A  +   java\testing\org\apache\derbyTesting\functionTests\tests\store\encryptionKey_jar.sql
A  +   java\testing\org\apache\derbyTesting\functionTests\tests\store\encryptionKey_jar_app.properties
A  +   java\testing\org\apache\derbyTesting\functionTests\master\encryptionKey_jar.out
M      java\testing\org\apache\derbyTesting\functionTests\suites\encryptionAll.runall

Ran derbyall on ibm142/linux ok.

Can someone please commit this change.


> Encrypted databases cannot be booted using the jar subprotocol (and possibly also using
> -------------------------------------------------------------------------------------------------------------
>                 Key: DERBY-1373
>                 URL: http://issues.apache.org/jira/browse/DERBY-1373
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions:
>         Environment: Environment does not matter.
>            Reporter: Mathias Herberts
>         Assigned To: Mathias Herberts
>             Fix For:
>         Attachments: 10.1_derby1373.diff.txt, derby1373.diff.txt, derby1373.stat.txt,
encryptedJar.patch, InputStreamFile.java-patch, InputStreamRandomAccessFile.java
> An encrypted database cannot be booted when using the jar subprotocol.
> The problem lies in the method run from JCECipherFactory. The call to getRandomAccessFile
returns null when the verifyKeyFile is an instance of InputStreamFile and the key verification
therefore fails.
> The implementation of getRandomAccessFile for InputStreamFile states that its code cannot
be reached which is untrue.
> The provided patch does two things, it provides a new class InputStreamRandomAccessFile
in package org.apache.derby.impl.io. This class provides simple implementations of readInt
and readFully so the key verification process succeeds. A quick scan of the derby source tree
showed no problem or possible impact of this simple implementation.
> The second thing the patch does is to modify org/apache/derby/impl/io/InputStreamFile.java
so the getRandomAccessFile creates an instance of InputStreamRandomAccessFile instead of returning
> This patch has been tested against trunk 410361. It solves the problem at least under
the jar subprotocol.
> The patch has not been tested against http/https/classpath.

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
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message