You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Roman S. Bushmanov (JIRA)" <ji...@apache.org> on 2007/05/23 13:02:16 UTC
[jira] Created: (HARMONY-3939) [classlib][security] Security
providers are initialized on fiest request
[classlib][security] Security providers are initialized on fiest 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
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.
[jira] Commented: (HARMONY-3939) [classlib][security] Security
providers are initialized on first request
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506690 ]
Vasily Zakharov commented on HARMONY-3939:
------------------------------------------
Yes, I have the similar concerns for HARMONY-2910.
I wonder if doPrivileged() in the stack should disable this AccessControlException but it does not?
> [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' prints 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.
[jira] Closed: (HARMONY-3939) [classlib][security] Security
providers are initialized on first request
Posted by "Tim Ellison (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Ellison closed HARMONY-3939.
--------------------------------
Resolution: Cannot Reproduce
Assignee: Tim Ellison
Roman, I am closing as cannot reproduce as you suggested.
If you want this re-opened that is not a problem, please let me know.
> [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
> Assignee: Tim Ellison
> 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' prints 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.
[jira] Updated: (HARMONY-3939) [classlib][security] Security
providers are initialized on first request
Posted by "Roman S. Bushmanov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman S. Bushmanov updated HARMONY-3939:
----------------------------------------
Description:
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' prints 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)
was:
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)
> [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' prints 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.
[jira] Commented: (HARMONY-3939) [classlib][security] Security
providers are initialized on first request
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507476 ]
Vasily Zakharov commented on HARMONY-3939:
------------------------------------------
I've investigated the situations where only DRL VM or only IBM VM failed security checks, and found that these situations disappear with the latest patch to HARMONY-2910 applied. So I assume no problem exists here.
> [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' prints 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.
[jira] Commented: (HARMONY-3939) [classlib][security] Security
providers are initialized on first request
Posted by "Mikhail Markov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506608 ]
Mikhail Markov commented on HARMONY-3939:
-----------------------------------------
I've checked Test1.java on latest snapshot and found that the problem is reproducible on J9 only (DRLVM prints the same output as RI).
I'm wondering - does it mean that DRLVM is not doing some security checkings which J9 does?
> [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' prints 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.
[jira] Updated: (HARMONY-3939) [classlib][security] Security
providers are initialized on first request
Posted by "Roman S. Bushmanov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman S. Bushmanov updated HARMONY-3939:
----------------------------------------
Attachment: Test.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.
[jira] Updated: (HARMONY-3939) [classlib][security] Security
providers are initialized on first request
Posted by "Roman S. Bushmanov (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HARMONY-3939) [classlib][security] Security
providers are initialized on first request
Posted by "Roman S. Bushmanov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506903 ]
Roman S. Bushmanov commented on HARMONY-3939:
---------------------------------------------
Mikhail, Vasily
I've checked r549123. Both the short reproducer test and the corresponding functional one work as expected.
So Harmony doesn't have such issue now:) Probably it was eliminated with fixes to other problems.
> [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' prints 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.
[jira] Commented: (HARMONY-3939) [classlib][security] Security
providers are initialized on first request
Posted by "Leo Li (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499672 ]
Leo Li commented on HARMONY-3939:
---------------------------------
After some studying I found that the problem is BouncyCastleProvider.addMappings does not have the priviledge to call java.security.Provider.put(Object, Object). Here is the stacktrace:
java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:195)
at org.apache.harmony.security.fortress.Engine.getInstance(Engine.java:91)
at java.security.AlgorithmParameters.getInstance(AlgorithmParameters.java:90)
at Test.main(Test.java:8)
Caused by: java.security.AccessControlException: Access denied (java.security.SecurityPermission putProviderProperty.BC)
at java.security.AccessController.checkPermission(AccessController.java:94)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:746)
at java.lang.SecurityManager.checkSecurityAccess(SecurityManager.java:422)
at java.security.Provider.put(Provider.java:236)
at org.bouncycastle.jce.provider.BouncyCastleProvider.addMappings(Unknown Source)
at org.bouncycastle.jce.provider.BouncyCastleProvider.<init>(Unknown Source)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1250)
at org.apache.harmony.security.fortress.Services.loadProviders(Services.java:84)
at org.apache.harmony.security.fortress.Services.access$0(Services.java:73)
at org.apache.harmony.security.fortress.Services$1.run(Services.java:66)
at java.security.AccessController.doPrivileged(AccessController.java:179)
at org.apache.harmony.security.fortress.Services.<clinit>(Services.java:64)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:177)
... 3 more
Harmony has such problem is that all the functions of bouncy castle reside in those classes in ext while RI, only those related to JCE is put in ext and other classes are in boot jars which have higher priviledges than former.
So if possible, part of the classes in bcprov.jar should be moved to boot directory of harmony.
> [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' prints 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.
[jira] Commented: (HARMONY-3939) [classlib][security] Security
providers are initialized on first request
Posted by "Vasily Zakharov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506943 ]
Vasily Zakharov commented on HARMONY-3939:
------------------------------------------
After the latest patch is applied to HARMONY-2910, this test works fine both on DRL VM and IBM VM.
So as soon as the patch to HARMONY-2910 is applied, this issue may be closed as "Cannot reproduce".
> [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' prints 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.
[jira] Updated: (HARMONY-3939) [classlib][security] Security
providers are initialized on first request
Posted by "Roman S. Bushmanov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-3939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman S. Bushmanov updated HARMONY-3939:
----------------------------------------
Summary: [classlib][security] Security providers are initialized on first request (was: [classlib][security] Security providers are initialized on fiest request)
> [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
>
> 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.