You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2007/05/08 12:51:15 UTC
[jira] Resolved: (DERBY-1001) Rewrite 'store/encryptionKey.sql' to
a JUnit test
[ 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: 10.3.0.0
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: 10.3.0.0
> Reporter: Kristian Waagan
> Assigned To: Kristian Waagan
> Priority: Minor
> Fix For: 10.3.0.0
>
> 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 above.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.