> If you also have tomcat-native installed…
No tomcat-native in any environment I saw, but I’ll make sure we check on that
config.
We’re not knowingly plugging Bouncy Castle into the Tomcat SSL mix at all. We
only use it in application logic after registering it with
Security.addProvider() in a
n"
Somewhere deep within Http11NioProtocol there is a bug that is fixed in
Http11Nio2Protocol. Unfortunately, we don’t have the bandwidth to try to
isolate it further, though I will update if anything else is uncovered.
Thanks,
Peter
On 7/20/16, 11:13 AM, "Peter Robbins" wrote:
That’s
GMT+02:00 Peter Robbins :
> Ok I'll see if I can dig BC out of the application and have it actually
> start up to try to see if that's the case.
>
> You're saying there are known compatibility issues with Tomcat NIO https
> if you register another j2ee security provider?
eem
crypto related apart from only appearing over https.
On Jul 20, 2016 1:56 AM, R?my Maucherat wrote:
2016-07-20 2:54 GMT+02:00 Peter Robbins :
> Without JCE or BC? Both are pretty critical for core functionality and
> didn't cause any issues until 8.5.3 entered the mix. Any known
Without JCE or BC? Both are pretty critical for core functionality and didn't
cause any issues until 8.5.3 entered the mix. Any known issues there I should
be aware of?
Peter
On Jul 19, 2016 6:24 PM, R?my Maucherat wrote:
2016-07-19 23:51 GMT+02:00 Peter Robbins :
> Hi there,
>
&g
Hi there,
Versions: Tomcat 8.5.3, JDK 1.8 + JCE, Bouncy Castle 1.48, Ubuntu 14.04 &
16.04,Windows 2012 R2
I’m running into an issue where we are getting NullPointerExceptions from the
Coyote connector in a Tomcat web application.
This is an existing, stable web application that was recently up
, so that being
the differentiator, I'll try my luck filing a bug with Oracle. >_<
I might play around and see if an APR setup demonstrates the same behavior.
Thanks,
Peter
On 11/13/14, 8:12 PM, "Christopher Schultz"
wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash:
I have SNI extension disabled with -Djsse.enableSNIExtension=false and
SSLv3 disabled with sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2". This
should just be vanilla TLS.
Peter
On 11/11/14, 10:12 PM, "Konstantin Kolinko" wrote:
>2014-11-12 0:03 GMT+03:00 Peter Robbin
Hi there,
I’m running into an issue with fully-qualified domain names and https
using Tomcat 8 and JDK 8.
Tomcat version: 8.0.14
JDK Version: 1.8.0_25OS: Mac OS X 10.10
If you include the trailing dot in a request over https, the TLS handshake
will fail. It appears that it tries to fall back to
