You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Kevin Mango <km...@nysif.com> on 2017/07/06 16:38:01 UTC
Errors establishing secure connections with tomcat 8.5.15
Hello,
I have been working to setup Apache Tomcat 8.5.15 to establish a secure connection to web applications on our server. However I have been having difficulties setting up this functionality.
The most meaningful error we have been getting is from Firefox, "Unsupported elliptic curve. Error code: SEC_ERROR_UNSUPPORTED_ELLIPTIC_CURVE". We have setup Tomcat to fully debug javax.net, and from these logs it appears that the handshake is failing at the server or client key exchanges. Below is the output after reaching the server key exchange:
ECDH ServerKeyExchange
Signature Algorithm SHA256withRSA
Server key: <key value>
*** ServerHelloDone
[write] MD5 and SHA1 hashes: len = 5073
<Large block of hex>
https-jsse-nio-8443-exec-3, WRITE: TLSv1.2 Handshake, length = 5073
[Raw write]: length = 5078
<Large block of hex>
https-jsse-nio-8443-exec-1, WRITE: TLSv1.2 Handshake, length = 5073
[Raw write]: length = 5078
<Large block of hex>
[Raw read]: length = 2
<small block of hex>
<Large block of hex>
https-jsse-nio-8443-exec-5, READ: TLSv1.2 Alert, length = 2
https-jsse-nio-8443-exec-5, RECV TLSv1.2 ALERT: fatal, illegal_parameter
https-jsse-nio-8443-exec-5, fatal: engine already closed. Rethrowing javax.net.ssl.SSLException: Received fatal alert: illegal_parameter
https-jsse-nio-8443-exec-5, fatal: engine already closed. Rethrowing javax.net.ssl.SSLException: Received fatal alert: illegal_parameter
https-jsse-nio-8443-exec-5, called closeOutbound()
https-jsse-nio-8443-exec-5, closeOutboundInternal()
https-jsse-nio-8443-exec-5, SEND TLSv1.2 ALERT: warning, description = close_notify
https-jsse-nio-8443-exec-5, WRITE: TLSv1.2 Alert, length = 2
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
There isn't any error output from stderr, only standard print statements. The ciphersuite that is chosen is TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256. Below are some details about the machine we are running tomcat on:
Windows Server 2012 R2 64 bit
16gb ram
2.2ghz intel xeon cpu
Java 1.8.131
Here is the connector in our server.xml file:
<Connector port="8443"
protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="200"
scheme="https" secure="true" SSLEnabled="true"
defaultSSLHostConfigName="<hostname> "
>
<SSLHostConfig
hostname="<hostname> "
protocols="TLSv1.2"
sslProtocol="TLSv1.2">
<Certificate certificateKeystoreFile="<pfx cert location and full file name>"
certificateKeystorePassword="<password>"
certificateKeystoreType="PKCS12"
type="RSA"/>
</SSLHostConfig>
</Connector>
Some additional notes:
1. The server we are running this on is internal and therefore can't be accessed outside our network
2. The web browser on the machine is unable to access the web application locally due to our network security
3. I am able to connect via http to the web apps
Any assistance that could be provided in this matter would be greatly appreciated.
Thank you,
Kevin
________________________________
This e-mail transmission contains confidential information that is the property of the sender. If you are not the intended recipient, you are notified that any retention, disclosure, reproduction or distribution of the contents of this e-mail transmission, or the taking of any action in reliance thereon or pursuant thereto, is strictly prohibited. No warranty is given by NYSIF that this e-mail is free of viruses, interception or interference. NYSIF disclaims liability for any unauthorized opinion, representation, statement, offer or contract made by the sender on behalf of NYSIF. NYSIF's delegation of authorities, setting out who may make representations or contract on behalf of NYSIF, is available by contacting NYSIF at mailadm@nysif.com. Jurisdiction for all actions arising out of dealings with NYSIF shall lie only in a court of competent jurisdiction of the State of New York
Re: Errors establishing secure connections with tomcat 8.5.15
Posted by Guang Chao <gu...@gmail.com>.
On Fri, Jul 7, 2017 at 9:51 PM, Kevin Mango <km...@nysif.com> wrote:
>
>
> -----Original Message-----
> From: André Warnier (tomcat) [mailto:aw@ice-sa.com]
> Sent: Friday, July 7, 2017 4:14 AM
> To: users@tomcat.apache.org
> Subject: Re: Errors establishing secure connections with tomcat 8.5.15
>
> 1) don't top-post
>
> On 07.07.2017 02:39, Guang Chao wrote:
> > Sorry, the Tomcat will connect to other web applications hosted
> > somewhere else in your network? Is my understanding correct?
> >
> > On Fri, Jul 7, 2017 at 12:38 AM, Kevin Mango <km...@nysif.com> wrote:
> >
> >> Hello,
> >>
> >> I have been working to setup Apache Tomcat 8.5.15 to establish a
> >> secure connection to web applications on our server. However I have
> >> been having difficulties setting up this functionality.
> >>
> >> The most meaningful error we have been getting is from Firefox,
> >> "Unsupported elliptic curve. Error code: SEC_ERROR_UNSUPPORTED_
> ELLIPTIC_CURVE".
> >> We have setup Tomcat to fully debug javax.net, and from these logs it
> >> appears that the handshake is failing at the server or client key
> >> exchanges. Below is the output after reaching the server key exchange:
> >>
> >> ECDH ServerKeyExchange
> >> Signature Algorithm SHA256withRSA
> >> Server key: <key value>
> >> *** ServerHelloDone
> >> [write] MD5 and SHA1 hashes: len = 5073 <Large block of hex>
> >> https-jsse-nio-8443-exec-3, WRITE: TLSv1.2 Handshake, length = 5073
> >> [Raw write]: length = 5078 <Large block of hex>
> >> https-jsse-nio-8443-exec-1, WRITE: TLSv1.2 Handshake, length = 5073
> >> [Raw write]: length = 5078 <Large block of hex> [Raw read]: length =
> >> 2 <small block of hex> <Large block of hex>
> >> https-jsse-nio-8443-exec-5, READ: TLSv1.2 Alert, length = 2
> >> https-jsse-nio-8443-exec-5, RECV TLSv1.2 ALERT: fatal,
> >> illegal_parameter https-jsse-nio-8443-exec-5, fatal: engine already
> >> closed. Rethrowing
> >> javax.net.ssl.SSLException: Received fatal alert: illegal_parameter
> >> https-jsse-nio-8443-exec-5, fatal: engine already closed. Rethrowing
> >> javax.net.ssl.SSLException: Received fatal alert: illegal_parameter
> >> https-jsse-nio-8443-exec-5, called closeOutbound()
> >> https-jsse-nio-8443-exec-5, closeOutboundInternal()
> >> https-jsse-nio-8443-exec-5, SEND TLSv1.2 ALERT: warning, description
> >> = close_notify https-jsse-nio-8443-exec-5, WRITE: TLSv1.2 Alert,
> >> length = 2
> >> ------------------------------------------------------------
> >> ------------------------------------------------------------
> >> ------------------------------------------------------------
> >> --------------------------
> >> There isn't any error output from stderr, only standard print
> statements.
> >> The ciphersuite that is chosen is TLS_ECDHE_RSA_WITH_AES_128_
> GCM_SHA256.
> >> Below are some details about the machine we are running tomcat on:
> >>
> >> Windows Server 2012 R2 64 bit
> >> 16gb ram
> >> 2.2ghz intel xeon cpu
> >> Java 1.8.131
> >>
> >> Here is the connector in our server.xml file:
> >>
> >> <Connector port="8443"
> >> protocol="org.apache.coyote.http11.Http11NioProtocol"
> >> maxThreads="200"
> >> scheme="https" secure="true" SSLEnabled="true"
> >> defaultSSLHostConfigName="<hostname> "
> >> >
> >> <SSLHostConfig
> >> hostname="<hostname> "
> >> protocols="TLSv1.2"
> >> sslProtocol="TLSv1.2">
> >> <Certificate certificateKeystoreFile="<pfx cert location
> >> and full file name>"
> >> certificateKeystorePassword="<password>"
> >> certificateKeystoreType="PKCS12"
> >> type="RSA"/>
> >> </SSLHostConfig>
> >>
> >> </Connector>
> >>
> >> Some additional notes:
> >>
> >> 1. The server we are running this on is internal and therefore
> >> can't be accessed outside our network
> >> 2. The web browser on the machine is unable to access the web
> >> application locally due to our network security
> >> 3. I am able to connect via http to the web apps
> >>
> >> Any assistance that could be provided in this matter would be greatly
> >> appreciated.
> >>
> >> Thank you,
> >> Kevin
> >>
> >>
>
> 2) One thing which you could/should try first, is to look at the Tomcat
> User's list archives.
> See : http://tomcat.apache.org/lists.html -> tomcat users -> archives
> There is a considrable amount of correspondence there related to such
> themes, and the answer you are looking for is probably already there.
> ---------------------------------------------------------------------
>
> @Guang Chao
> No the web apps are installed in the tomcat webapps folder, I am able to
> access these web apps through http, but when trying to connect through
> https it fails to connect with ssl errors, with Firefox's unsupported
> elliptical curve error being the most meaningful.
>
I am not sure if I have mentioned earlier, very sorry if I already did.
But how about using a reverse proxy? Could be easier to install ssl on
nginx, then have nginx between your browser and tomcat?
>
> @André Warnier
> I will look through the archive and see if I can find anything helpful.
> Thank you.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
> ________________________________
> This e-mail transmission contains confidential information that is the
> property of the sender. If you are not the intended recipient, you are
> notified that any retention, disclosure, reproduction or distribution of
> the contents of this e-mail transmission, or the taking of any action in
> reliance thereon or pursuant thereto, is strictly prohibited. No warranty
> is given by NYSIF that this e-mail is free of viruses, interception or
> interference. NYSIF disclaims liability for any unauthorized opinion,
> representation, statement, offer or contract made by the sender on behalf
> of NYSIF. NYSIF's delegation of authorities, setting out who may make
> representations or contract on behalf of NYSIF, is available by contacting
> NYSIF at mailadm@nysif.com. Jurisdiction for all actions arising out of
> dealings with NYSIF shall lie only in a court of competent jurisdiction of
> the State of New York
>
--
Guang <http://javadevnotes.com/java-left-pad-string-with-zeros-examples/>
RE: Errors establishing secure connections with tomcat 8.5.15
Posted by Kevin Mango <km...@nysif.com>.
-----Original Message-----
From: Christopher Schultz [mailto:chris@christopherschultz.net]
Sent: Thursday, July 13, 2017 4:32 PM
To: users@tomcat.apache.org
Subject: Re: Errors establishing secure connections with tomcat 8.5.15
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Kevin,
On 7/11/17 3:48 PM, Kevin Mango wrote:
>
>
> -----Original Message----- From: Christopher Schultz
> [mailto:chris@christopherschultz.net] Sent: Tuesday, July 11, 2017
> 1:58 PM To: users@tomcat.apache.org Subject: Re: Errors establishing
> secure connections with tomcat 8.5.15
>
> Kevin,
>
> On 7/7/17 12:40 PM, Kevin Mango wrote:
>> I was able to resolve this by using
>> "-Dcom.sun.net.ssl.enableECC=false" when starting tomcat to disable
>> the use of Elliptic Curves, the only issue now is that Google Chrome
>> is having issues finding a common cipher suite to use, giving the
>> error ERR_SSL_VERSION_OR_CIPHER_MISMATCH.
>
> Your configuration does not include any specification for cipher
> suites:
>
>>>> Here is the connector in our server.xml file:
>>>>
>>>> <Connector port="8443"
>>>> protocol="org.apache.coyote.http11.Http11NioProtocol"
>>>> maxThreads="200" scheme="https" secure="true"
>>>> SSLEnabled="true" defaultSSLHostConfigName="<hostname> "
>>>>>
>>>> <SSLHostConfig hostname="<hostname> " protocols="TLSv1.2"
>>>> sslProtocol="TLSv1.2"> <Certificate certificateKeystoreFile="<pfx
>>>> cert location and full file
>>>> name>" certificateKeystorePassword="<password>"
>>>> certificateKeystoreType="PKCS12" type="RSA"/> </SSLHostConfig>
>>>>
>>>> </Connector>
>
> So it would be unusual for a client and server not to be able to agree
> on a cipher suite.
>
> Are you adjusting the available cipher suites any other way (e.g.
> system property that affects JSSE, edits to
> $JAVA_HOME/jre/security/*.policy, etc.)?
>
> What kind of certificate are you using? Is it an ECC certificate
> (rather than the more common RSA certificates)?
>
> -chris
> ---------------------------------------------------------------------
>
>
Hi Chris,
>
> I 'm not adjusting the cipher suites in any way. My *.policy files are
> the default ones that came with the JDK installation, same with the
> .security file. The only thing I changed in that directory was adding
> the Unlimited Strength policy JAR's.
>
> As for the certificates, we are using self-signed RSA certificates.
>
> On our older machines that are running Tomcat 7 and JDK 7, these
> certificates work fine for our purposes and are still working. In
> these cases the handshake uses the cipher ECDHE-RSA-AES128-GCM-SHA256.
> But with Tomcat 8.5.15 and JDK 8 we have been getting error's with
> unsupported elliptic curve, even when it uses the same or similar
> cipher suites.
>
> Additionally I have tried debugging this with OpenSSL, but when trying
> to connect it gives an error message "SSL
> routines:tls_process_ske_ecdhe:wrong
> curve:ssl\statem\statem_clnt.c:2057:". Even when specifying curves and
> cipher suites into the OpenSSL client connection, I continue to get
> this error.
>
> The only thing that has come close to working for us is by using
> "-Dcom.sun.net.ssl.enableECC=false" when starting Tomcat to disable
> all EC ciphers, but Google Chrome won't accept the connection due to
> being unable to find a common cipher suite.
Can you try "repairing" your Java installation to restore the original policy files? I've added the Unlimited Cipher Strength Policy Files before and it's fairly straightforward, but I'm wondering if maybe you botched the installation of those and broke the JRE.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJZZ9i/AAoJEBzwKT+lPKRYNc4QALtN5E8EXuPDhXh7p+MhrSZk
y8/YWeGo10mFS6mvD89QiHrYl6dzvmu9EXctlGCsQ+tS/u/4at3T9wN/eqx9E5X2
UokD2NoaC1P8D/dWNGq2c+p0UONX6g//w1UNeS4//b2OfW/AfiSut45jifiaNI+G
2iXIiT90cv9JzvRKPD3X48SH2SXm55SqMz+EzV59ajR8HDJRflEKIzrqCV/5pXuI
oT9Sxbh++daE78+h0TgHI0d2O9sWJQRlswzg5Kmt9pJ3Yu08sgKP1hFADfZeKM/b
XeOVh+BqwnkEQhwubO5aL6UOKaww2IGhZZiWJo0sOzP/uGTiDfe4Mk8vw1Sa1hXo
H90sSaBAsGHQE65VjDAJqOMlqYDcckO89wHbBmcS4f19VMiQwv8qHzn4n1ci+jpg
z/jkmpHNFkXoHWL0fF5ZJj7CrVoJ6NGihE1qPziyxveWiPex7G1gGrMsrFGPea+i
2BdAil4FnM5YUOwRaThGsS88JHbfRalh/N3N+EhxOuubNT13z/YWul5rdzr1XfRC
fzWiJS0Mu3nUPV5FVjt9sQ6AVeviw3vNpQ6uNZbnRahl9W7y4mCLxe4EmNmE6VwB
/O+xBlCHyb69ONGCJTAPPUrYwN+hMz9bjh0R2Quq+bngt6ns/IvR10ZAulKvni+j
jY52Cnq+IVL+GjY5Mn18
=pmjM
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
When I installed the Unlimited Strength files I just copied them into the security folder and overwrote the existing JARs that were there. I reverted this folder after I was getting these errors and it appeared to do nothing, and then I added them back in.
Though we managed to find a solution to this. Instead of using a JSSE connector we are instead using the APR and OpenSSL. I was able to take our current pfx file and extract the certificate and key into separate files that Tomcat now can use in the connection.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
________________________________
This e-mail transmission contains confidential information that is the property of the sender. If you are not the intended recipient, you are notified that any retention, disclosure, reproduction or distribution of the contents of this e-mail transmission, or the taking of any action in reliance thereon or pursuant thereto, is strictly prohibited. No warranty is given by NYSIF that this e-mail is free of viruses, interception or interference. NYSIF disclaims liability for any unauthorized opinion, representation, statement, offer or contract made by the sender on behalf of NYSIF. NYSIF's delegation of authorities, setting out who may make representations or contract on behalf of NYSIF, is available by contacting NYSIF at mailadm@nysif.com. Jurisdiction for all actions arising out of dealings with NYSIF shall lie only in a court of competent jurisdiction of the State of New York
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Errors establishing secure connections with tomcat 8.5.15
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Kevin,
On 7/11/17 3:48 PM, Kevin Mango wrote:
>
>
> -----Original Message----- From: Christopher Schultz
> [mailto:chris@christopherschultz.net] Sent: Tuesday, July 11, 2017
> 1:58 PM To: users@tomcat.apache.org Subject: Re: Errors
> establishing secure connections with tomcat 8.5.15
>
> Kevin,
>
> On 7/7/17 12:40 PM, Kevin Mango wrote:
>> I was able to resolve this by using
>> "-Dcom.sun.net.ssl.enableECC=false" when starting tomcat to
>> disable the use of Elliptic Curves, the only issue now is that
>> Google Chrome is having issues finding a common cipher suite to
>> use, giving the error ERR_SSL_VERSION_OR_CIPHER_MISMATCH.
>
> Your configuration does not include any specification for cipher
> suites:
>
>>>> Here is the connector in our server.xml file:
>>>>
>>>> <Connector port="8443"
>>>> protocol="org.apache.coyote.http11.Http11NioProtocol"
>>>> maxThreads="200" scheme="https" secure="true"
>>>> SSLEnabled="true" defaultSSLHostConfigName="<hostname> "
>>>>>
>>>> <SSLHostConfig hostname="<hostname> " protocols="TLSv1.2"
>>>> sslProtocol="TLSv1.2"> <Certificate
>>>> certificateKeystoreFile="<pfx cert location and full file
>>>> name>" certificateKeystorePassword="<password>"
>>>> certificateKeystoreType="PKCS12" type="RSA"/>
>>>> </SSLHostConfig>
>>>>
>>>> </Connector>
>
> So it would be unusual for a client and server not to be able to
> agree on a cipher suite.
>
> Are you adjusting the available cipher suites any other way (e.g.
> system property that affects JSSE, edits to
> $JAVA_HOME/jre/security/*.policy, etc.)?
>
> What kind of certificate are you using? Is it an ECC certificate
> (rather than the more common RSA certificates)?
>
> -chris
> ---------------------------------------------------------------------
>
>
Hi Chris,
>
> I 'm not adjusting the cipher suites in any way. My *.policy files
> are the default ones that came with the JDK installation, same with
> the .security file. The only thing I changed in that directory was
> adding the Unlimited Strength policy JAR's.
>
> As for the certificates, we are using self-signed RSA
> certificates.
>
> On our older machines that are running Tomcat 7 and JDK 7, these
> certificates work fine for our purposes and are still working. In
> these cases the handshake uses the cipher
> ECDHE-RSA-AES128-GCM-SHA256. But with Tomcat 8.5.15 and JDK 8 we
> have been getting error's with unsupported elliptic curve, even
> when it uses the same or similar cipher suites.
>
> Additionally I have tried debugging this with OpenSSL, but when
> trying to connect it gives an error message "SSL
> routines:tls_process_ske_ecdhe:wrong
> curve:ssl\statem\statem_clnt.c:2057:". Even when specifying curves
> and cipher suites into the OpenSSL client connection, I continue to
> get this error.
>
> The only thing that has come close to working for us is by using
> "-Dcom.sun.net.ssl.enableECC=false" when starting Tomcat to disable
> all EC ciphers, but Google Chrome won't accept the connection due
> to being unable to find a common cipher suite.
Can you try "repairing" your Java installation to restore the original
policy files? I've added the Unlimited Cipher Strength Policy Files
before and it's fairly straightforward, but I'm wondering if maybe you
botched the installation of those and broke the JRE.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJZZ9i/AAoJEBzwKT+lPKRYNc4QALtN5E8EXuPDhXh7p+MhrSZk
y8/YWeGo10mFS6mvD89QiHrYl6dzvmu9EXctlGCsQ+tS/u/4at3T9wN/eqx9E5X2
UokD2NoaC1P8D/dWNGq2c+p0UONX6g//w1UNeS4//b2OfW/AfiSut45jifiaNI+G
2iXIiT90cv9JzvRKPD3X48SH2SXm55SqMz+EzV59ajR8HDJRflEKIzrqCV/5pXuI
oT9Sxbh++daE78+h0TgHI0d2O9sWJQRlswzg5Kmt9pJ3Yu08sgKP1hFADfZeKM/b
XeOVh+BqwnkEQhwubO5aL6UOKaww2IGhZZiWJo0sOzP/uGTiDfe4Mk8vw1Sa1hXo
H90sSaBAsGHQE65VjDAJqOMlqYDcckO89wHbBmcS4f19VMiQwv8qHzn4n1ci+jpg
z/jkmpHNFkXoHWL0fF5ZJj7CrVoJ6NGihE1qPziyxveWiPex7G1gGrMsrFGPea+i
2BdAil4FnM5YUOwRaThGsS88JHbfRalh/N3N+EhxOuubNT13z/YWul5rdzr1XfRC
fzWiJS0Mu3nUPV5FVjt9sQ6AVeviw3vNpQ6uNZbnRahl9W7y4mCLxe4EmNmE6VwB
/O+xBlCHyb69ONGCJTAPPUrYwN+hMz9bjh0R2Quq+bngt6ns/IvR10ZAulKvni+j
jY52Cnq+IVL+GjY5Mn18
=pmjM
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Errors establishing secure connections with tomcat 8.5.15
Posted by Kevin Mango <km...@nysif.com>.
-----Original Message-----
From: Christopher Schultz [mailto:chris@christopherschultz.net]
Sent: Tuesday, July 11, 2017 1:58 PM
To: users@tomcat.apache.org
Subject: Re: Errors establishing secure connections with tomcat 8.5.15
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Kevin,
On 7/7/17 12:40 PM, Kevin Mango wrote:
> I was able to resolve this by using
> "-Dcom.sun.net.ssl.enableECC=false" when starting tomcat to disable
> the use of Elliptic Curves, the only issue now is that Google Chrome
> is having issues finding a common cipher suite to use, giving the
> error ERR_SSL_VERSION_OR_CIPHER_MISMATCH.
Your configuration does not include any specification for cipher suites:
>>> Here is the connector in our server.xml file:
>>>
>>> <Connector port="8443"
>>> protocol="org.apache.coyote.http11.Http11NioProtocol"
>>> maxThreads="200" scheme="https" secure="true"
>>> SSLEnabled="true" defaultSSLHostConfigName="<hostname> "
>>>>
>>> <SSLHostConfig hostname="<hostname> " protocols="TLSv1.2"
>>> sslProtocol="TLSv1.2"> <Certificate
>>> certificateKeystoreFile="<pfx cert location and full file
>>> name>" certificateKeystorePassword="<password>"
>>> certificateKeystoreType="PKCS12" type="RSA"/> </SSLHostConfig>
>>>
>>> </Connector>
So it would be unusual for a client and server not to be able to agree on a cipher suite.
Are you adjusting the available cipher suites any other way (e.g.
system property that affects JSSE, edits to $JAVA_HOME/jre/security/*.policy, etc.)?
What kind of certificate are you using? Is it an ECC certificate (rather than the more common RSA certificates)?
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJZZRGfAAoJEBzwKT+lPKRYXw4P/Rp2LJILdM0w5xVpVoyF/yyo
PCj3TWJPMS2F188gYZnpAEj69bXjfP7nIvFt0JpWN6VYhYkLaiOKot9IUp7aRUBQ
jJgJqJ7LEVA2pS9fE+ioQV0APdchXKhuab3iiRs+dikulJWhvWPO+8+N7jzCrhvQ
iohHdmnOK8DdoJdd9OL1j/+vWPj3Bwc9sucR4DCvEeCZ2jG+zRNDM0mFcwqSkz0T
0QdEdvbj6VeBQTJiGRFVGF+RncdTH2D266Jh/8Xc3DUut8sQEI/gUrlSSluFw33e
B9Aye4V20c8KJ5gJ92pCyGHbsOkdxgQobKvfOp/2UlYJyGZxQcfabLN99wc8TPqm
mHxvq9s3eEYCesvd1AiVGeguO8Pmdg62ml5/CR7/QIJFXKvXmn+IxTsqj+1VWDmK
QqQmvw8vwVEDXMYppzT4UX8UX9xWWGLEGL5eOTgcsI81Qeo0sBO5r1KojhNgv1kl
JB/1V0jS4RJ3E4BzOPMM+lB3DOwHpdtVFPotQq+4bVI8W87bM2nQL3mGZvBsMF6Q
Zj9FWUB5d7wS0KLeOlIJANQT+1kwjbK1i08irwmLYCqQyrUq7+csR+xh1TZRKuhT
paVCNRmx7Xryk/kWQf4g2d0yoSwJhTduIgMmrrLqIUY6UNfjZtNXF4fX5q93nnvP
F6twQiax7locrje76JUo
=0o+S
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
Hi Chris,
I 'm not adjusting the cipher suites in any way. My *.policy files are the default ones that came with the JDK installation, same with the .security file. The only thing I changed in that directory was adding the Unlimited Strength policy JAR's.
As for the certificates, we are using self-signed RSA certificates.
On our older machines that are running Tomcat 7 and JDK 7, these certificates work fine for our purposes and are still working. In these cases the handshake uses the cipher ECDHE-RSA-AES128-GCM-SHA256. But with Tomcat 8.5.15 and JDK 8 we have been getting error's with unsupported elliptic curve, even when it uses the same or similar cipher suites.
Additionally I have tried debugging this with OpenSSL, but when trying to connect it gives an error message "SSL routines:tls_process_ske_ecdhe:wrong curve:ssl\statem\statem_clnt.c:2057:". Even when specifying curves and cipher suites into the OpenSSL client connection, I continue to get this error.
The only thing that has come close to working for us is by using "-Dcom.sun.net.ssl.enableECC=false" when starting Tomcat to disable all EC ciphers, but Google Chrome won't accept the connection due to being unable to find a common cipher suite.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
________________________________
This e-mail transmission contains confidential information that is the property of the sender. If you are not the intended recipient, you are notified that any retention, disclosure, reproduction or distribution of the contents of this e-mail transmission, or the taking of any action in reliance thereon or pursuant thereto, is strictly prohibited. No warranty is given by NYSIF that this e-mail is free of viruses, interception or interference. NYSIF disclaims liability for any unauthorized opinion, representation, statement, offer or contract made by the sender on behalf of NYSIF. NYSIF's delegation of authorities, setting out who may make representations or contract on behalf of NYSIF, is available by contacting NYSIF at mailadm@nysif.com. Jurisdiction for all actions arising out of dealings with NYSIF shall lie only in a court of competent jurisdiction of the State of New York
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Errors establishing secure connections with tomcat 8.5.15
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Kevin,
On 7/7/17 12:40 PM, Kevin Mango wrote:
> I was able to resolve this by using
> "-Dcom.sun.net.ssl.enableECC=false" when starting tomcat to disable
> the use of Elliptic Curves, the only issue now is that Google
> Chrome is having issues finding a common cipher suite to use,
> giving the error ERR_SSL_VERSION_OR_CIPHER_MISMATCH.
Your configuration does not include any specification for cipher suites:
>>> Here is the connector in our server.xml file:
>>>
>>> <Connector port="8443"
>>> protocol="org.apache.coyote.http11.Http11NioProtocol"
>>> maxThreads="200" scheme="https" secure="true"
>>> SSLEnabled="true" defaultSSLHostConfigName="<hostname> "
>>>>
>>> <SSLHostConfig hostname="<hostname> " protocols="TLSv1.2"
>>> sslProtocol="TLSv1.2"> <Certificate
>>> certificateKeystoreFile="<pfx cert location and full file
>>> name>" certificateKeystorePassword="<password>"
>>> certificateKeystoreType="PKCS12" type="RSA"/> </SSLHostConfig>
>>>
>>> </Connector>
So it would be unusual for a client and server not to be able to agree
on a cipher suite.
Are you adjusting the available cipher suites any other way (e.g.
system property that affects JSSE, edits to
$JAVA_HOME/jre/security/*.policy, etc.)?
What kind of certificate are you using? Is it an ECC certificate
(rather than the more common RSA certificates)?
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJZZRGfAAoJEBzwKT+lPKRYXw4P/Rp2LJILdM0w5xVpVoyF/yyo
PCj3TWJPMS2F188gYZnpAEj69bXjfP7nIvFt0JpWN6VYhYkLaiOKot9IUp7aRUBQ
jJgJqJ7LEVA2pS9fE+ioQV0APdchXKhuab3iiRs+dikulJWhvWPO+8+N7jzCrhvQ
iohHdmnOK8DdoJdd9OL1j/+vWPj3Bwc9sucR4DCvEeCZ2jG+zRNDM0mFcwqSkz0T
0QdEdvbj6VeBQTJiGRFVGF+RncdTH2D266Jh/8Xc3DUut8sQEI/gUrlSSluFw33e
B9Aye4V20c8KJ5gJ92pCyGHbsOkdxgQobKvfOp/2UlYJyGZxQcfabLN99wc8TPqm
mHxvq9s3eEYCesvd1AiVGeguO8Pmdg62ml5/CR7/QIJFXKvXmn+IxTsqj+1VWDmK
QqQmvw8vwVEDXMYppzT4UX8UX9xWWGLEGL5eOTgcsI81Qeo0sBO5r1KojhNgv1kl
JB/1V0jS4RJ3E4BzOPMM+lB3DOwHpdtVFPotQq+4bVI8W87bM2nQL3mGZvBsMF6Q
Zj9FWUB5d7wS0KLeOlIJANQT+1kwjbK1i08irwmLYCqQyrUq7+csR+xh1TZRKuhT
paVCNRmx7Xryk/kWQf4g2d0yoSwJhTduIgMmrrLqIUY6UNfjZtNXF4fX5q93nnvP
F6twQiax7locrje76JUo
=0o+S
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Errors establishing secure connections with tomcat 8.5.15
Posted by Kevin Mango <km...@nysif.com>.
I was able to resolve this by using "-Dcom.sun.net.ssl.enableECC=false" when starting tomcat to disable the use of Elliptic Curves, the only issue now is that Google Chrome is having issues finding a common cipher suite to use, giving the error ERR_SSL_VERSION_OR_CIPHER_MISMATCH.
-----Original Message-----
From: Kevin Mango [mailto:kmango@nysif.com]
Sent: Friday, July 7, 2017 9:52 AM
To: Tomcat Users List <us...@tomcat.apache.org>
Subject: RE: Errors establishing secure connections with tomcat 8.5.15
-----Original Message-----
From: André Warnier (tomcat) [mailto:aw@ice-sa.com]
Sent: Friday, July 7, 2017 4:14 AM
To: users@tomcat.apache.org
Subject: Re: Errors establishing secure connections with tomcat 8.5.15
1) don't top-post
On 07.07.2017 02:39, Guang Chao wrote:
> Sorry, the Tomcat will connect to other web applications hosted
> somewhere else in your network? Is my understanding correct?
>
> On Fri, Jul 7, 2017 at 12:38 AM, Kevin Mango <km...@nysif.com> wrote:
>
>> Hello,
>>
>> I have been working to setup Apache Tomcat 8.5.15 to establish a
>> secure connection to web applications on our server. However I have
>> been having difficulties setting up this functionality.
>>
>> The most meaningful error we have been getting is from Firefox,
>> "Unsupported elliptic curve. Error code: SEC_ERROR_UNSUPPORTED_ELLIPTIC_CURVE".
>> We have setup Tomcat to fully debug javax.net, and from these logs it
>> appears that the handshake is failing at the server or client key
>> exchanges. Below is the output after reaching the server key exchange:
>>
>> ECDH ServerKeyExchange
>> Signature Algorithm SHA256withRSA
>> Server key: <key value>
>> *** ServerHelloDone
>> [write] MD5 and SHA1 hashes: len = 5073 <Large block of hex>
>> https-jsse-nio-8443-exec-3, WRITE: TLSv1.2 Handshake, length = 5073
>> [Raw write]: length = 5078 <Large block of hex>
>> https-jsse-nio-8443-exec-1, WRITE: TLSv1.2 Handshake, length = 5073
>> [Raw write]: length = 5078 <Large block of hex> [Raw read]: length =
>> 2 <small block of hex> <Large block of hex>
>> https-jsse-nio-8443-exec-5, READ: TLSv1.2 Alert, length = 2
>> https-jsse-nio-8443-exec-5, RECV TLSv1.2 ALERT: fatal,
>> illegal_parameter https-jsse-nio-8443-exec-5, fatal: engine already
>> closed. Rethrowing
>> javax.net.ssl.SSLException: Received fatal alert: illegal_parameter
>> https-jsse-nio-8443-exec-5, fatal: engine already closed. Rethrowing
>> javax.net.ssl.SSLException: Received fatal alert: illegal_parameter
>> https-jsse-nio-8443-exec-5, called closeOutbound()
>> https-jsse-nio-8443-exec-5, closeOutboundInternal()
>> https-jsse-nio-8443-exec-5, SEND TLSv1.2 ALERT: warning, description
>> = close_notify https-jsse-nio-8443-exec-5, WRITE: TLSv1.2 Alert,
>> length = 2
>> ------------------------------------------------------------
>> ------------------------------------------------------------
>> ------------------------------------------------------------
>> --------------------------
>> There isn't any error output from stderr, only standard print statements.
>> The ciphersuite that is chosen is TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
>> Below are some details about the machine we are running tomcat on:
>>
>> Windows Server 2012 R2 64 bit
>> 16gb ram
>> 2.2ghz intel xeon cpu
>> Java 1.8.131
>>
>> Here is the connector in our server.xml file:
>>
>> <Connector port="8443"
>> protocol="org.apache.coyote.http11.Http11NioProtocol"
>> maxThreads="200"
>> scheme="https" secure="true" SSLEnabled="true"
>> defaultSSLHostConfigName="<hostname> "
>> >
>> <SSLHostConfig
>> hostname="<hostname> "
>> protocols="TLSv1.2"
>> sslProtocol="TLSv1.2">
>> <Certificate certificateKeystoreFile="<pfx cert location
>> and full file name>"
>> certificateKeystorePassword="<password>"
>> certificateKeystoreType="PKCS12"
>> type="RSA"/>
>> </SSLHostConfig>
>>
>> </Connector>
>>
>> Some additional notes:
>>
>> 1. The server we are running this on is internal and therefore
>> can't be accessed outside our network
>> 2. The web browser on the machine is unable to access the web
>> application locally due to our network security
>> 3. I am able to connect via http to the web apps
>>
>> Any assistance that could be provided in this matter would be greatly
>> appreciated.
>>
>> Thank you,
>> Kevin
>>
>>
2) One thing which you could/should try first, is to look at the Tomcat User's list archives.
See : http://tomcat.apache.org/lists.html -> tomcat users -> archives There is a considrable amount of correspondence there related to such themes, and the answer you are looking for is probably already there.
---------------------------------------------------------------------
@Guang Chao
No the web apps are installed in the tomcat webapps folder, I am able to access these web apps through http, but when trying to connect through https it fails to connect with ssl errors, with Firefox's unsupported elliptical curve error being the most meaningful.
@André Warnier
I will look through the archive and see if I can find anything helpful. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
________________________________
This e-mail transmission contains confidential information that is the property of the sender. If you are not the intended recipient, you are notified that any retention, disclosure, reproduction or distribution of the contents of this e-mail transmission, or the taking of any action in reliance thereon or pursuant thereto, is strictly prohibited. No warranty is given by NYSIF that this e-mail is free of viruses, interception or interference. NYSIF disclaims liability for any unauthorized opinion, representation, statement, offer or contract made by the sender on behalf of NYSIF. NYSIF's delegation of authorities, setting out who may make representations or contract on behalf of NYSIF, is available by contacting NYSIF at mailadm@nysif.com. Jurisdiction for all actions arising out of dealings with NYSIF shall lie only in a court of competent jurisdiction of the State of New York
________________________________
This e-mail transmission contains confidential information that is the property of the sender. If you are not the intended recipient, you are notified that any retention, disclosure, reproduction or distribution of the contents of this e-mail transmission, or the taking of any action in reliance thereon or pursuant thereto, is strictly prohibited. No warranty is given by NYSIF that this e-mail is free of viruses, interception or interference. NYSIF disclaims liability for any unauthorized opinion, representation, statement, offer or contract made by the sender on behalf of NYSIF. NYSIF's delegation of authorities, setting out who may make representations or contract on behalf of NYSIF, is available by contacting NYSIF at mailadm@nysif.com. Jurisdiction for all actions arising out of dealings with NYSIF shall lie only in a court of competent jurisdiction of the State of New York
RE: Errors establishing secure connections with tomcat 8.5.15
Posted by Kevin Mango <km...@nysif.com>.
-----Original Message-----
From: André Warnier (tomcat) [mailto:aw@ice-sa.com]
Sent: Friday, July 7, 2017 4:14 AM
To: users@tomcat.apache.org
Subject: Re: Errors establishing secure connections with tomcat 8.5.15
1) don't top-post
On 07.07.2017 02:39, Guang Chao wrote:
> Sorry, the Tomcat will connect to other web applications hosted
> somewhere else in your network? Is my understanding correct?
>
> On Fri, Jul 7, 2017 at 12:38 AM, Kevin Mango <km...@nysif.com> wrote:
>
>> Hello,
>>
>> I have been working to setup Apache Tomcat 8.5.15 to establish a
>> secure connection to web applications on our server. However I have
>> been having difficulties setting up this functionality.
>>
>> The most meaningful error we have been getting is from Firefox,
>> "Unsupported elliptic curve. Error code: SEC_ERROR_UNSUPPORTED_ELLIPTIC_CURVE".
>> We have setup Tomcat to fully debug javax.net, and from these logs it
>> appears that the handshake is failing at the server or client key
>> exchanges. Below is the output after reaching the server key exchange:
>>
>> ECDH ServerKeyExchange
>> Signature Algorithm SHA256withRSA
>> Server key: <key value>
>> *** ServerHelloDone
>> [write] MD5 and SHA1 hashes: len = 5073 <Large block of hex>
>> https-jsse-nio-8443-exec-3, WRITE: TLSv1.2 Handshake, length = 5073
>> [Raw write]: length = 5078 <Large block of hex>
>> https-jsse-nio-8443-exec-1, WRITE: TLSv1.2 Handshake, length = 5073
>> [Raw write]: length = 5078 <Large block of hex> [Raw read]: length =
>> 2 <small block of hex> <Large block of hex>
>> https-jsse-nio-8443-exec-5, READ: TLSv1.2 Alert, length = 2
>> https-jsse-nio-8443-exec-5, RECV TLSv1.2 ALERT: fatal,
>> illegal_parameter https-jsse-nio-8443-exec-5, fatal: engine already
>> closed. Rethrowing
>> javax.net.ssl.SSLException: Received fatal alert: illegal_parameter
>> https-jsse-nio-8443-exec-5, fatal: engine already closed. Rethrowing
>> javax.net.ssl.SSLException: Received fatal alert: illegal_parameter
>> https-jsse-nio-8443-exec-5, called closeOutbound()
>> https-jsse-nio-8443-exec-5, closeOutboundInternal()
>> https-jsse-nio-8443-exec-5, SEND TLSv1.2 ALERT: warning, description
>> = close_notify https-jsse-nio-8443-exec-5, WRITE: TLSv1.2 Alert,
>> length = 2
>> ------------------------------------------------------------
>> ------------------------------------------------------------
>> ------------------------------------------------------------
>> --------------------------
>> There isn't any error output from stderr, only standard print statements.
>> The ciphersuite that is chosen is TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
>> Below are some details about the machine we are running tomcat on:
>>
>> Windows Server 2012 R2 64 bit
>> 16gb ram
>> 2.2ghz intel xeon cpu
>> Java 1.8.131
>>
>> Here is the connector in our server.xml file:
>>
>> <Connector port="8443"
>> protocol="org.apache.coyote.http11.Http11NioProtocol"
>> maxThreads="200"
>> scheme="https" secure="true" SSLEnabled="true"
>> defaultSSLHostConfigName="<hostname> "
>> >
>> <SSLHostConfig
>> hostname="<hostname> "
>> protocols="TLSv1.2"
>> sslProtocol="TLSv1.2">
>> <Certificate certificateKeystoreFile="<pfx cert location
>> and full file name>"
>> certificateKeystorePassword="<password>"
>> certificateKeystoreType="PKCS12"
>> type="RSA"/>
>> </SSLHostConfig>
>>
>> </Connector>
>>
>> Some additional notes:
>>
>> 1. The server we are running this on is internal and therefore
>> can't be accessed outside our network
>> 2. The web browser on the machine is unable to access the web
>> application locally due to our network security
>> 3. I am able to connect via http to the web apps
>>
>> Any assistance that could be provided in this matter would be greatly
>> appreciated.
>>
>> Thank you,
>> Kevin
>>
>>
2) One thing which you could/should try first, is to look at the Tomcat User's list archives.
See : http://tomcat.apache.org/lists.html -> tomcat users -> archives There is a considrable amount of correspondence there related to such themes, and the answer you are looking for is probably already there.
---------------------------------------------------------------------
@Guang Chao
No the web apps are installed in the tomcat webapps folder, I am able to access these web apps through http, but when trying to connect through https it fails to connect with ssl errors, with Firefox's unsupported elliptical curve error being the most meaningful.
@André Warnier
I will look through the archive and see if I can find anything helpful. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
________________________________
This e-mail transmission contains confidential information that is the property of the sender. If you are not the intended recipient, you are notified that any retention, disclosure, reproduction or distribution of the contents of this e-mail transmission, or the taking of any action in reliance thereon or pursuant thereto, is strictly prohibited. No warranty is given by NYSIF that this e-mail is free of viruses, interception or interference. NYSIF disclaims liability for any unauthorized opinion, representation, statement, offer or contract made by the sender on behalf of NYSIF. NYSIF's delegation of authorities, setting out who may make representations or contract on behalf of NYSIF, is available by contacting NYSIF at mailadm@nysif.com. Jurisdiction for all actions arising out of dealings with NYSIF shall lie only in a court of competent jurisdiction of the State of New York
Re: Errors establishing secure connections with tomcat 8.5.15
Posted by "André Warnier (tomcat)" <aw...@ice-sa.com>.
1) don't top-post
On 07.07.2017 02:39, Guang Chao wrote:
> Sorry, the Tomcat will connect to other web applications hosted somewhere
> else in your network? Is my understanding correct?
>
> On Fri, Jul 7, 2017 at 12:38 AM, Kevin Mango <km...@nysif.com> wrote:
>
>> Hello,
>>
>> I have been working to setup Apache Tomcat 8.5.15 to establish a secure
>> connection to web applications on our server. However I have been having
>> difficulties setting up this functionality.
>>
>> The most meaningful error we have been getting is from Firefox,
>> "Unsupported elliptic curve. Error code: SEC_ERROR_UNSUPPORTED_ELLIPTIC_CURVE".
>> We have setup Tomcat to fully debug javax.net, and from these logs it
>> appears that the handshake is failing at the server or client key
>> exchanges. Below is the output after reaching the server key exchange:
>>
>> ECDH ServerKeyExchange
>> Signature Algorithm SHA256withRSA
>> Server key: <key value>
>> *** ServerHelloDone
>> [write] MD5 and SHA1 hashes: len = 5073
>> <Large block of hex>
>> https-jsse-nio-8443-exec-3, WRITE: TLSv1.2 Handshake, length = 5073
>> [Raw write]: length = 5078
>> <Large block of hex>
>> https-jsse-nio-8443-exec-1, WRITE: TLSv1.2 Handshake, length = 5073
>> [Raw write]: length = 5078
>> <Large block of hex>
>> [Raw read]: length = 2
>> <small block of hex>
>> <Large block of hex>
>> https-jsse-nio-8443-exec-5, READ: TLSv1.2 Alert, length = 2
>> https-jsse-nio-8443-exec-5, RECV TLSv1.2 ALERT: fatal, illegal_parameter
>> https-jsse-nio-8443-exec-5, fatal: engine already closed. Rethrowing
>> javax.net.ssl.SSLException: Received fatal alert: illegal_parameter
>> https-jsse-nio-8443-exec-5, fatal: engine already closed. Rethrowing
>> javax.net.ssl.SSLException: Received fatal alert: illegal_parameter
>> https-jsse-nio-8443-exec-5, called closeOutbound()
>> https-jsse-nio-8443-exec-5, closeOutboundInternal()
>> https-jsse-nio-8443-exec-5, SEND TLSv1.2 ALERT: warning, description =
>> close_notify
>> https-jsse-nio-8443-exec-5, WRITE: TLSv1.2 Alert, length = 2
>> ------------------------------------------------------------
>> ------------------------------------------------------------
>> ------------------------------------------------------------
>> --------------------------
>> There isn't any error output from stderr, only standard print statements.
>> The ciphersuite that is chosen is TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
>> Below are some details about the machine we are running tomcat on:
>>
>> Windows Server 2012 R2 64 bit
>> 16gb ram
>> 2.2ghz intel xeon cpu
>> Java 1.8.131
>>
>> Here is the connector in our server.xml file:
>>
>> <Connector port="8443"
>> protocol="org.apache.coyote.http11.Http11NioProtocol"
>> maxThreads="200"
>> scheme="https" secure="true" SSLEnabled="true"
>> defaultSSLHostConfigName="<hostname> "
>> >
>> <SSLHostConfig
>> hostname="<hostname> "
>> protocols="TLSv1.2"
>> sslProtocol="TLSv1.2">
>> <Certificate certificateKeystoreFile="<pfx cert location and
>> full file name>"
>> certificateKeystorePassword="<password>"
>> certificateKeystoreType="PKCS12"
>> type="RSA"/>
>> </SSLHostConfig>
>>
>> </Connector>
>>
>> Some additional notes:
>>
>> 1. The server we are running this on is internal and therefore can't be
>> accessed outside our network
>> 2. The web browser on the machine is unable to access the web
>> application locally due to our network security
>> 3. I am able to connect via http to the web apps
>>
>> Any assistance that could be provided in this matter would be greatly
>> appreciated.
>>
>> Thank you,
>> Kevin
>>
>>
2) One thing which you could/should try first, is to look at the Tomcat User's list archives.
See : http://tomcat.apache.org/lists.html -> tomcat users -> archives
There is a considrable amount of correspondence there related to such themes, and the
answer you are looking for is probably already there.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Errors establishing secure connections with tomcat 8.5.15
Posted by Guang Chao <gu...@gmail.com>.
Sorry, the Tomcat will connect to other web applications hosted somewhere
else in your network? Is my understanding correct?
On Fri, Jul 7, 2017 at 12:38 AM, Kevin Mango <km...@nysif.com> wrote:
> Hello,
>
> I have been working to setup Apache Tomcat 8.5.15 to establish a secure
> connection to web applications on our server. However I have been having
> difficulties setting up this functionality.
>
> The most meaningful error we have been getting is from Firefox,
> "Unsupported elliptic curve. Error code: SEC_ERROR_UNSUPPORTED_ELLIPTIC_CURVE".
> We have setup Tomcat to fully debug javax.net, and from these logs it
> appears that the handshake is failing at the server or client key
> exchanges. Below is the output after reaching the server key exchange:
>
> ECDH ServerKeyExchange
> Signature Algorithm SHA256withRSA
> Server key: <key value>
> *** ServerHelloDone
> [write] MD5 and SHA1 hashes: len = 5073
> <Large block of hex>
> https-jsse-nio-8443-exec-3, WRITE: TLSv1.2 Handshake, length = 5073
> [Raw write]: length = 5078
> <Large block of hex>
> https-jsse-nio-8443-exec-1, WRITE: TLSv1.2 Handshake, length = 5073
> [Raw write]: length = 5078
> <Large block of hex>
> [Raw read]: length = 2
> <small block of hex>
> <Large block of hex>
> https-jsse-nio-8443-exec-5, READ: TLSv1.2 Alert, length = 2
> https-jsse-nio-8443-exec-5, RECV TLSv1.2 ALERT: fatal, illegal_parameter
> https-jsse-nio-8443-exec-5, fatal: engine already closed. Rethrowing
> javax.net.ssl.SSLException: Received fatal alert: illegal_parameter
> https-jsse-nio-8443-exec-5, fatal: engine already closed. Rethrowing
> javax.net.ssl.SSLException: Received fatal alert: illegal_parameter
> https-jsse-nio-8443-exec-5, called closeOutbound()
> https-jsse-nio-8443-exec-5, closeOutboundInternal()
> https-jsse-nio-8443-exec-5, SEND TLSv1.2 ALERT: warning, description =
> close_notify
> https-jsse-nio-8443-exec-5, WRITE: TLSv1.2 Alert, length = 2
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------------------------------------------
> --------------------------
> There isn't any error output from stderr, only standard print statements.
> The ciphersuite that is chosen is TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.
> Below are some details about the machine we are running tomcat on:
>
> Windows Server 2012 R2 64 bit
> 16gb ram
> 2.2ghz intel xeon cpu
> Java 1.8.131
>
> Here is the connector in our server.xml file:
>
> <Connector port="8443"
> protocol="org.apache.coyote.http11.Http11NioProtocol"
> maxThreads="200"
> scheme="https" secure="true" SSLEnabled="true"
> defaultSSLHostConfigName="<hostname> "
> >
> <SSLHostConfig
> hostname="<hostname> "
> protocols="TLSv1.2"
> sslProtocol="TLSv1.2">
> <Certificate certificateKeystoreFile="<pfx cert location and
> full file name>"
> certificateKeystorePassword="<password>"
> certificateKeystoreType="PKCS12"
> type="RSA"/>
> </SSLHostConfig>
>
> </Connector>
>
> Some additional notes:
>
> 1. The server we are running this on is internal and therefore can't be
> accessed outside our network
> 2. The web browser on the machine is unable to access the web
> application locally due to our network security
> 3. I am able to connect via http to the web apps
>
> Any assistance that could be provided in this matter would be greatly
> appreciated.
>
> Thank you,
> Kevin
>
>
>
> ________________________________
> This e-mail transmission contains confidential information that is the
> property of the sender. If you are not the intended recipient, you are
> notified that any retention, disclosure, reproduction or distribution of
> the contents of this e-mail transmission, or the taking of any action in
> reliance thereon or pursuant thereto, is strictly prohibited. No warranty
> is given by NYSIF that this e-mail is free of viruses, interception or
> interference. NYSIF disclaims liability for any unauthorized opinion,
> representation, statement, offer or contract made by the sender on behalf
> of NYSIF. NYSIF's delegation of authorities, setting out who may make
> representations or contract on behalf of NYSIF, is available by contacting
> NYSIF at mailadm@nysif.com. Jurisdiction for all actions arising out of
> dealings with NYSIF shall lie only in a court of competent jurisdiction of
> the State of New York
>
--
Guang
<http://javadevnotes.com/java-double-to-string-2-decimal-places-examples/>