Chris,
On Mon, Oct 26, 2020 at 2:34 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> If you still need this, then you really need to upgrade your Java. Java
> 8 no longer requires application of a separate, "unlimited" policy file
> since u162, released January 2018.
>
Good to kno
Steve,
On 10/26/20 13:02, Steve Sanders wrote:
We ran into similar issues when upgrading to latest JDK 8 (and 11). We
found that the fix was to add the sun.security.ec.SunEC as a security
provider in java.security like so:
security.provider.9=sun.security.ec.SunEC
I'll have to try that. I can
Hi Chris,
We ran into similar issues when upgrading to latest JDK 8 (and 11). We
found that the fix was to add the sun.security.ec.SunEC as a security
provider in java.security like so:
security.provider.9=sun.security.ec.SunEC
After adding this we were able to continue using our current certifi
All,
(Note that this has nothing whatsoever to to with Apache Tomcat. These
connections are between services running on Tomcat and others, but
Tomcat's TLS code or configuration is in no way involved.)
I recently upgraded my OpenJDK Java 8 installations on a few servers and
started getting t
