On 7.4.2015 15:23, Christopher Schultz wrote:
After a weekend of ripping out clumps of my hair and swearing at my
computer, nothing had worked. In desperation, before upgrading
Java and Tomcat, I tried regenerating my self-signed certificate
with new settings (SHA256 instead of SHA1) and that s
ed in
your configuration. Re-generating the TLS certificate might have ended
some of the warnings about certs with a SHA-1 signature, but the
cipher-mismatch is a different beast and probably more important.
- -chris
> -Original Message----- From: Terence M. Bandoian Sent: Monday,
Terence M. Bandoian
Sent: Monday, April 06, 2015 12:21 PM
To: Tomcat Users List
Subject: Re: Need configuration example for Tomcat 7.0.55 TLS configuration
On 4/6/2015 2:11 AM, Ognjen Blagojevic wrote:
Tom,
On 5.4.2015 3:06, Tom Williamson wrote:
I would like to know if anyone has a working e
We're on Tomcat 8 with Java 8, so it has more options for ciphers, but
this is what we use:
protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true"
connectionTimeout="2" acceptorThreadCount="2"
URIEncoding="UTF-8"
maxThreads="100" scheme="h
On 4/6/2015 2:11 AM, Ognjen Blagojevic wrote:
Tom,
On 5.4.2015 3:06, Tom Williamson wrote:
I would like to know if anyone has a working example of getting TLS 1.2
working on Tomcat 7.0.55, so that it can be accessed by the latest
version of Chrome and Firefox.
Which version of Java do you use
Tom,
On 5.4.2015 3:06, Tom Williamson wrote:
I would like to know if anyone has a working example of getting TLS 1.2
working on Tomcat 7.0.55, so that it can be accessed by the latest
version of Chrome and Firefox.
Which version of Java do you use? Make sure it is Java 7 or 8, and if
you alre
