harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boris Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] Created: (HARMONY-430) security tests failures
Date Tue, 02 May 2006 09:45:46 GMT
security tests failures

         Key: HARMONY-430
         URL: http://issues.apache.org/jira/browse/HARMONY-430
     Project: Harmony
        Type: Bug

  Components: Classlib  
    Reporter: Boris Kuznetsov

I have analyzed security tests failures.
Here are the results.

<exclude name="java/security/serialization/KeyPairTest.java"/>
It is impossible create correct golden file for KeyPair because the serialized form must contain
fields of PrivateKey and PublicKey types (PrivateKey and PublicKey are interfaces and all
implementations are provider specific). This test uses golden file that refers to sun.security.provider.DSAPrivateKey.
So this test should be removed or completely rewritten (only "self-testing" is possible).

<exclude name="java/security/serialization/AccessControlExceptionTest.java"/>
<exclude name="java/security/serialization/InvalidParameterExceptionTest.java"/>
These two tests successfully passed.

<exclude name="tests/api/java/security/AccessControllerTest.java"/>
This test is designed to run via classpath.

<exclude name="tests/api/java/security/AlgorithmParameterGeneratorTest.java"/>
<exclude name="tests/api/java/security/AlgorithmParametersTest.java"/>
Tests are fixed.

<exclude name="tests/api/java/security/KeyStoreTest.java"/>
This test failed due BC provider bug. Will file separate issue.

<exclude name="tests/api/java/security/PermissionCollectionTest.java"/>
This test is designed to run via classpath.

<exclude name="tests/api/java/security/SecureRandomTest.java"/>
This test requers SHA1PRNG SecureRandom. But no SHA1PRNG implementation yet.

<exclude name="tests/api/java/security/SecurityTest.java"/>
java.security.Security and SecurityTest are fixed.

I will attach a patch shortly.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message