Hello all,
I've updated the webrev with all of Adam's findings with one exception.
I did try bringing the crypto provider code in-line. That approach will
work for OpenJDK where there is no 3rd party signing requirement, but on
Oracle JDK it will not and the provider needs to be in the form
On 15/03/2019 17:58, Hohensee, Paul wrote:
> +1
>
> Paul
>
> On 3/15/19, 4:00 AM, "jdk8u-dev on behalf of Aleksey Shipilev"
> wrote:
>
> On 3/15/19 5:55 AM, Andrew John Hughes wrote:
> > Bug: https://bugs.openjdk.java.net/browse/JDK-8220641
> > Webrev:
On 3/15/19 5:55 AM, Andrew John Hughes wrote:
> Bug: https://bugs.openjdk.java.net/browse/JDK-8220641
> Webrev: https://cr.openjdk.java.net/~andrew/openjdk8/8220641/webrev.01/
Looks good, ship it.
-Aleksey
signature.asc
Description: OpenPGP digital signature
+1
Paul
On 3/15/19, 4:00 AM, "jdk8u-dev on behalf of Aleksey Shipilev"
wrote:
On 3/15/19 5:55 AM, Andrew John Hughes wrote:
> Bug: https://bugs.openjdk.java.net/browse/JDK-8220641
> Webrev: https://cr.openjdk.java.net/~andrew/openjdk8/8220641/webrev.01/
Looks good, ship
FYI if anyone is interested in using OpenSSL through a Java security
Provider we have this project available within the WildFly project: -
https://github.com/wildfly/wildfly-openssl
On Fri, Mar 15, 2019 at 9:48 AM Steve Groeger wrote:
> Hi all,
>
> Not sure whether something on this subject
Hi,
We were trying to simplify the certificate and SSL configuration during our
java app deployment in Windows. As part of this, we were trying to pull
certificates from Windows-ROOT or Windows-MY by setting
System.setProperty("javax.net.ssl.trustStoreType","Windows-ROOT");
Actually this is not based on OpenSSL but it uses BoringSSL (which provides an
OpenSSL API + some extra stuff), just in case it matters for anyone.
Bye
Norman
> On 15. Mar 2019, at 17:37, Simone Bordet wrote:
>
> Hi,
>
> On Fri, Mar 15, 2019 at 3:28 PM Darran Lofthouse
> wrote:
>> FYI if
Martin,
> 1) Is this integrated to the JCE crypto providers framework or does it
work separately?
No, this is not currently integrated into the JCE crypto providers
framework.
The implementation we currently have integrates into the existing JCE
providers and it defaults to using the OpenSSL
FYI if anyone is interested in using OpenSSL through a Java security
Provider we have this project available within the WildFly project: -
https://github.com/wildfly/wildfly-openssl
On Fri, Mar 15, 2019 at 9:48 AM Steve Groeger wrote:
> Hi all,
>
> Not sure whether something on this subject
Hi Steve,
This looks interesting.
I have a couple of questions:
1) Is this integrated to the JCE crypto providers framework or does it
work separately? The properties "jdk.nativeCrypto" and
"jdk.nativeDigest" made me think it's not.
2) Which algorithms are under scope?
Kind regards,
Martin.-
Hi Steve,
This looks interesting.
I have a couple of questions:
1) Is this integrated to the JCE crypto providers framework or does it
work separately? The properties "jdk.nativeCrypto" and
"jdk.nativeDigest" made me think it's not.
2) Which algorithms are under scope?
Kind regards,
Martin.-
Hi all,
Not sure whether something on this subject has been raised before but I
was unable to see anything in the mailing lists.
We have been looking at adding support to Java to use the OpenSSL
libraries as a JCE security provider if available on the system that a
Java application is being
Hi Andrew,
On Fri, 2019-03-15 at 04:55 +, Andrew John Hughes wrote:
> Bug: https://bugs.openjdk.java.net/browse/JDK-8220641
> Webrev:
> https://cr.openjdk.java.net/~andrew/openjdk8/8220641/webrev.01/
>
> This is the patch we split out from my original post for 8175120. It
> applies the same
13 matches
Mail list logo
