[ https://issues.apache.org/jira/browse/HARMONY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman S. Bushmanov updated HARMONY-3939:
----------------------------------------
Attachment: Test1.java
> [classlib][security] Security providers are initialized on first request
> ------------------------------------------------------------------------
>
> Key: HARMONY-3939
> URL: https://issues.apache.org/jira/browse/HARMONY-3939
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Environment: Windows/ia32
> Reporter: Roman S. Bushmanov
> Attachments: Test.java, Test1.java
>
>
> Security providers can be initialized correctly only by trusted code i.e. application
working w/out security manager or application with certain security permission granted.
> At the same time, JavaTM Cryptography Architecture API Specification & Reference
requires the code to be trusted only for *dynamic* registration of provoders and no security
permissions are required to install a provider by means of java.security file.
> To reproduce the problem please run two simple testcases on the same JRE. These two
testcases differs in one line which ilstalls a security manager and expected output is the
same.
> 'Test' testcase produces on svn = r537794, (May 14 2007), Windows/ia32/msvc 1310, release
build the following output:
> DSA
> while 'Test1' print the following
> java.security.NoSuchAlgorithmException: AlgorithmParameters DSA implementation not found
> at org.apache.harmony.security.fortress.Engine.getInstance(Engine.java:111)
> at java.security.AlgorithmParameters.getInstance(AlgorithmParameters.java:90)
> at Test1.main(Test1.java:9)
> On RI both testcases prints the same:
> DSA
> Affected tests:
> functional/org/apache/harmony/test/func/api/java/security/F_AlgorithmParametersTest_01/F_AlgorithmParametersTest_01.xml
> (see HARMONY-3528)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|