Hello Glen,
JCE providers are always accessed via the Java SE public APIs and not directly
via sun.* implementation classes.
In JDK 9, the SunPKCS11 provider continues to be accessible via those APIs.
It’s implementation classes are present
in the jdk.crypto.pkcs11 module.
Thanks.
> On 16 No
Vincent, Max, can you push the change now? Just don't want that it gets
forgotten...
Thanks
Christoph
-Original Message-
From: Wang Weijun [mailto:weijun.w...@oracle.com]
Sent: Montag, 16. November 2015 08:32
To: Vincent Ryan
Cc: Langer, Christoph ; security-dev@openjdk.java.net
Subjec
On 11/16/2015 08:00 PM, Wang Weijun wrote:
On Nov 16, 2015, at 11:46 PM, Sean Mullan wrote:
Provider p = Security.getProvider("SunPKCS11");
p.configure("/opt/bar/cfg/pkcs11.cfg");
p = p.configure("/opt/bar/cfg/pkcs11.cfg");
The spec for the method says:
* Apply the supplied config
On 11/17/2015 09:10 AM, Wang Weijun wrote:
Hi All
The test has failed a lot recently. Please review the change:
diff --git a/test/ProblemList.txt b/test/ProblemList.txt
--- a/test/ProblemList.txt
+++ b/test/ProblemList.txt
@@ -234,6 +234,7 @@
sun/security/tools/jarsigner/warnings/BadKeyUsageT
Hi All
The test has failed a lot recently. Please review the change:
diff --git a/test/ProblemList.txt b/test/ProblemList.txt
--- a/test/ProblemList.txt
+++ b/test/ProblemList.txt
@@ -234,6 +234,7 @@
sun/security/tools/jarsigner/warnings/BadKeyUsageTest.java generic-all
# 8077138: Some PK
Hi Amanda
On 11/17/2015 15:03, Amanda Jiang wrote:
http://cr.openjdk.java.net/~amjiang/8048357/webrev.03/
Why "othervm" for all these tests?
The pkcs10 and pkcs8 tests still uses othervm. Is that necessary? I see
no VM static change made by these tests.
PKCS8Test.java:
- sun.security.x5
