Re: Vulnerability on Apache Tomcat Default Files

Hi Chris, Did that as well, but the scanner still flagged but it is to say is a false positive result in their scan? Regards with Thanks, Fang On Wed, 5 Aug 2020, 04:21 Christopher Schultz, wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Fang, > > On 8/3/20 23:10, FANG YAP

Re: Let's Encrypt cert worked fine in 8.5.57, but connector fails in 8.5.40

On 8/5/20 5:04 PM, calder wrote: Caused by: java.security.KeyStoreException: Cannot store non-PrivateKeys If you pasted the full stack trace, then here we have the last "caused by", showing one issue at sun.security.provider.JavaKeyStore.engineSetKeyEntry(JavaKeyStore.java:261)

Re: Let's Encrypt cert worked fine in 8.5.57, but connector fails in 8.5.40

On Wed, Aug 5, 2020, 18:46 James H. H. Lampert wrote: > Ladies and Gentlemen: > > I've now proceeded to the "real" server, with the Tomcat portion of the > procedure refined to give me plenty of "undo" capability. And it turns > out I need it. > > It seems that with the unwanted update to 7.0.57

Correction, Re: Let's Encrypt cert worked fine in 8.5.57, but connector fails in 8.5.40

I wrote: . . . It seems that with the unwanted update to 7.0.57 that happened on launching the test spot instances, the Let's Encrypt certs worked just fine. But applying the procedure to the *real* development instance (7.0.40) blew up in my face, failing to open the connectors. Here is an

Let's Encrypt cert worked fine in 8.5.57, but connector fails in 8.5.40

Ladies and Gentlemen: I've now proceeded to the "real" server, with the Tomcat portion of the procedure refined to give me plenty of "undo" capability. And it turns out I need it. It seems that with the unwanted update to 7.0.57 that happened on launching the test spot instances, the Let's

RE: Connector works fine with Firefox, but not on speaking terms with Chrome!

Good job with those tests and good luck with the real site! Dream * Excel * Explore * Inspire Jon McAlexander Asst Vice President Middleware Product Engineering Enterprise CIO | Platform Services | Middleware | Infrastructure Solutions 8080 Cobblestone Rd | Urbandale, IA 50322 MAC: F4469-010

Re: Connector works fine with Firefox, but not on speaking terms with Chrome!

Jon Mcalexander wrote: Most likely then you need to find a cypher list that is valid for TLSv1.2. Such as below: ACCEPTABLE TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

RE: Connector works fine with Firefox, but not on speaking terms with Chrome!

-Original Message- From: James H. H. Lampert Sent: Wednesday, August 5, 2020 1:06 PM To: Tomcat Users List Subject: Re: Connector works fine with Firefox, but not on speaking terms with Chrome! On 8/5/20 10:43 AM, calder wrote: > certificateVerificationh="none" > > there's one

Re: Connector works fine with Firefox, but not on speaking terms with Chrome!

On 8/5/20 10:43 AM, calder wrote: certificateVerificationh="none" there's one issue (misspelling), though may not be a contributing factor. Corrected; no effect. Jon McAlexander wrote: I believe that protocols="TLSv1.2"> should be sslEnabledProtocol="TLSv1.2" My understanding of the

RE: Connector works fine with Firefox, but not on speaking terms with Chrome!

I believe that protocols="TLSv1.2"> should be sslEnabledProtocol="TLSv1.2" Dream * Excel * Explore * Inspire Jon McAlexander Asst Vice President Middleware Product Engineering Enterprise CIO | Platform Services | Middleware | Infrastructure Solutions 8080 Cobblestone Rd | Urbandale, IA

Re: Connector works fine with Firefox, but not on speaking terms with Chrome!

On Wed, Aug 5, 2020, 12:22 James H. H. Lampert wrote: > I've now managed to get an experimental copy of our development AWS EC2 > instance working with a cert from Let's Encrypt, and I've got Tomcat to > launch with a modified connector that uses the LE certs rather than a > Java Keystore file.

Connector works fine with Firefox, but not on speaking terms with Chrome!

I've now managed to get an experimental copy of our development AWS EC2 instance working with a cert from Let's Encrypt, and I've got Tomcat to launch with a modified connector that uses the LE certs rather than a Java Keystore file. It looks great from Firefox (except for the still-unanswered