db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-1001) Rewrite 'store/encryptionKey.sql' to a JUnit test
Date Tue, 08 May 2007 10:51:15 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kristian Waagan resolved DERBY-1001.

       Resolution: Fixed
    Fix Version/s:
       Derby Info:   (was: [Patch Available])

Committed 'derby-1001-2a.diff' to trunk with revision 536156.

Three different algorithms are currently tested: AES, DES and Blowfish.
Streaming ciphers do not currently work with Derby.

> Rewrite 'store/encryptionKey.sql' to a JUnit test
> -------------------------------------------------
>                 Key: DERBY-1001
>                 URL: https://issues.apache.org/jira/browse/DERBY-1001
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions:
>            Reporter: Kristian Waagan
>         Assigned To: Kristian Waagan
>            Priority: Minor
>             Fix For:
>         Attachments: derby-1001-1a-preliminary.diff, derby-1001-1a-preliminary.stat,
derby-1001-2a.diff, derby-1001-2a.stat
> This test has failed on Solaris10 for a long time, due to issues with the default security
provider on this OS. See DERBY-788 for details.
> I consider rewriting this test as interresting because it allows us to see how things
can be done in "the JUnit way". 
> 1) Run test with multiple encryption algorithms with minimal test code duplication.
> 2) Special handling of exceptions for specific providers (PCKS11-Solaris).
> The rewritten test might cause some discussion on how we want to handle the issues mentioned

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message