You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Richard Huntrods <hu...@nucleus.com> on 2019/04/09 21:48:27 UTC
Problem with SSH in latest Tomcat
Greetings!
I would like to 'do what's necessary' to remove the following error.
Google tells me it's related to my security implementation, which is
HTTPS by default. I am convinced the problem is in how I invoke the port
443 connector in my server.xml. I've been running this servlet on
versions of Tomcat since 2001, and have kept my Tomcat instances up to
date. Most recently I started noticing this in the logs, and
am pretty sure it's because I've been copying the connector code bit
from server.xml to server.xml as I upgraded versions of Tomcat.
I really suspect my connector is now out-of-date and could use some
guideance as to the best new form. I see in the recent server.xml they
use a different involcation, but don't know if this is best...
OS: Ubuntu 18.04 LTS Live server
Tomcat: 8.5.39, installed from tar.gz obtained from Tomcat.
I've done this enough times to "get it right", so it's just this Hello
error I want to eradicate...
Here is the error message:
08-Apr-2019 01:00:23.477 SEVERE [https-jsse-nio-443-exec-9]
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
java.lang.UnsupportedOperationException: Unsupported SSL v2.0 ClientHello
at
java.base/sun.security.ssl.SSLEngineInputRecord.handleUnknownRecord(SSLEngineInputRecord.java:373)
at
java.base/sun.security.ssl.SSLEngineInputRecord.decode(SSLEngineInputRecord.java:195)
at
java.base/sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:975)
at
java.base/sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:902)
at
java.base/sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:680)
at java.base/javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:626)
at
org.apache.tomcat.util.net.SecureNioChannel.handshakeUnwrap(SecureNioChannel.java:475)
at
org.apache.tomcat.util.net.SecureNioChannel.handshake(SecureNioChannel.java:238)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1475)
at
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.base/java.lang.Thread.run(Thread.java:844)
My certificates are new and correct, and have run fine in past versions
of Tomcat without problems...
THIS IS MY SERVER.XML - Most of it is identical to the server.xml
supplied with Tomcat 8.5.39 My changes are after the *** THIS IS MY
CONNECTOR ... *** comment.
Thanks,
-Richard
**********************
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" at this level.
Documentation at /docs/config/server.html
-->
<Server port="8005" shutdown="SHUTDOWN">
<Listener
className="org.apache.catalina.startup.VersionLoggerListener" />
<!-- Security listener. Documentation at /docs/config/listeners.html
<Listener className="org.apache.catalina.security.SecurityListener" />
-->
<!--APR library loader. Documentation at /docs/apr.html -->
<!-- <Listener
className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on"
/> -->
<!-- Prevent memory leaks due to use of particular java/javax APIs-->
<Listener
className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
<Listener
className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
<Listener
className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />
<!-- Global JNDI resources
Documentation at /docs/jndi-resources-howto.html
-->
<GlobalNamingResources>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users
-->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved"
factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
pathname="conf/tomcat-users.xml" />
</GlobalNamingResources>
<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" Note: A "Service" is not itself a "Container",
so you may not define subcomponents such as "Valves" at this level.
Documentation at /docs/config/service.html
-->
<Service name="Catalina">
<!--The connectors can use a shared executor, you can define one or
more named thread pools-->
<!--
<Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
maxThreads="150" minSpareThreads="4"/>
-->
<!-- A "Connector" represents an endpoint by which requests are
received
and responses are returned. Documentation at :
Java HTTP Connector: /docs/config/http.html
Java AJP Connector: /docs/config/ajp.html
APR (HTTP/AJP) Connector: /docs/apr.html
Define a non-SSL/TLS HTTP/1.1 Connector on port 8080
-->
<!--
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443" />
-->
<Connector port="80" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="443" />
<!-- A "Connector" using the shared thread pool-->
<!--
<Connector executor="tomcatThreadPool"
port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443" />
-->
<!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443
This connector uses the NIO implementation. The default
SSLImplementation will depend on the presence of the APR/native
library and the useOpenSSL attribute of the
AprLifecycleListener.
Either JSSE or OpenSSL style configuration may be used
regardless of
the SSLImplementation selected. JSSE style configuration is
used below.
-->
<!--
<Connector port="8443"
protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150" SSLEnabled="true">
<SSLHostConfig>
<Certificate certificateKeystoreFile="conf/localhost-rsa.jks"
type="RSA" />
</SSLHostConfig>
</Connector>
-->
<!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443 with HTTP/2
This connector uses the APR/native implementation which always
uses
OpenSSL for TLS.
Either JSSE or OpenSSL style configuration may be used.
OpenSSL style
configuration is used below.
-->
<!--
<Connector port="8443"
protocol="org.apache.coyote.http11.Http11AprProtocol"
maxThreads="150" SSLEnabled="true" >
<UpgradeProtocol
className="org.apache.coyote.http2.Http2Protocol" />
<SSLHostConfig>
<Certificate certificateKeyFile="conf/localhost-rsa-key.pem"
certificateFile="conf/localhost-rsa-cert.pem"
certificateChainFile="conf/localhost-rsa-chain.pem"
type="RSA" />
</SSLHostConfig>
</Connector>
-->
<!-- *** THIS IS MY CONNECTOR FOR PORT 443: COPIED FROM PAST TOMCAT
VERSIONS *** -->
<Connector port="443" protocol="HTTP/1.1" SSLEnabled="true"
maxThreads="150" enableLookups="false" scheme="https"
secure="true"
keystoreFile="./keys/.keystore" keystorePass="password"
clientAuth="false" sslProtocol="TLS" />
<!-- Define an AJP 1.3 Connector on port 8009 -->
<!--
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />
-->
<!-- An Engine represents the entry point (within Catalina) that
processes
every request. The Engine implementation for Tomcat stand alone
analyzes the HTTP headers included with the request, and
passes them
on to the appropriate Host (virtual host).
Documentation at /docs/config/engine.html -->
<!-- You should set jvmRoute to support load-balancing via AJP ie :
<Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">
-->
<Engine name="Catalina" defaultHost="localhost">
<!--For clustering, please take a look at documentation at:
/docs/cluster-howto.html (simple how to)
/docs/config/cluster.html (reference documentation) -->
<!--
<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
-->
<!-- Use the LockOutRealm to prevent attempts to guess user passwords
via a brute-force attack -->
<Realm className="org.apache.catalina.realm.LockOutRealm">
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
resourceName="UserDatabase"/>
</Realm>
<Host name="localhost" appBase="webapps"
unpackWARs="true" autoDeploy="true">
<!-- SingleSignOn valve, share authentication between web
applications
Documentation at: /docs/config/valve.html -->
<!--
<Valve
className="org.apache.catalina.authenticator.SingleSignOn" />
-->
<!-- Access log processes all example.
Documentation at: /docs/config/valve.html
Note: The pattern used is equivalent to using
pattern="common" -->
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs"
prefix="localhost_access_log" suffix=".txt"
pattern="%h %l %u %t "%r" %s %b" />
<Valve className="org.apache.catalina.valves.ErrorReportValve"
showReport="false" showServerInfo="false" />
</Host>
</Engine>
</Service>
</Server>
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problem with SSH in latest Tomcat
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Richard,
On 4/9/19 17:48, Richard Huntrods wrote:
> I would like to 'do what's necessary' to remove the following
> error. Google tells me it's related to my security implementation,
> which is HTTPS by default. I am convinced the problem is in how I
> invoke the port 443 connector in my server.xml. I've been running
> this servlet on versions of Tomcat since 2001, and have kept my
> Tomcat instances up to date. Most recently I started noticing this
> in the logs, and am pretty sure it's because I've been copying the
> connector code bit from server.xml to server.xml as I upgraded
> versions of Tomcat.
With a few exceptions, the <Connector /> configuration hasn't changed
a lot since then. The TLS configuration changed recently to be more
expressive and allow for more complex configurations, but the old
syntax should still work in many cases.
> I really suspect my connector is now out-of-date and could use
> some guidance as to the best new form. I see in the recent
> server.xml they use a different invocation, but don't know if this
> is best...
>
> OS: Ubuntu 18.04 LTS Live server Tomcat: 8.5.39, installed from
> tar.gz obtained from Tomcat.
What is the Java version?
> I've done this enough times to "get it right", so it's just this
> Hello error I want to eradicate...
:)
> Here is the error message:
>
> 08-Apr-2019 01:00:23.477 SEVERE [https-jsse-nio-443-exec-9]
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun
> java.lang.UnsupportedOperationException: Unsupported SSL v2.0
> ClientHello at
> java.base/sun.security.ssl.SSLEngineInputRecord.handleUnknownRecord(SS
LEngineInputRecord.java:373)
>
> at
> java.base/sun.security.ssl.SSLEngineInputRecord.decode(SSLEngineInputR
ecord.java:195)
>
> at
> java.base/sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java
:975)
>
>
at
> java.base/sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.j
ava:902)
>
> at
> java.base/sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:680
)
>
>
at java.base/javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:626)
> at
> org.apache.tomcat.util.net.SecureNioChannel.handshakeUnwrap(SecureNioC
hannel.java:475)
>
> at
> org.apache.tomcat.util.net.SecureNioChannel.handshake(SecureNioChannel
.java:238)
>
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoi
nt.java:1475)
>
> at
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase
.java:49)
>
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
Executor.java:1135)
>
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
lExecutor.java:635)
>
> at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThr
ead.java:61)
>
> at java.base/java.lang.Thread.run(Thread.java:844)
>
> My certificates are new and correct, and have run fine in past
> versions of Tomcat without problems...
>
> THIS IS MY SERVER.XML - Most of it is identical to the server.xml
> supplied with Tomcat 8.5.39 My changes are after the *** THIS IS
> MY CONNECTOR ... *** comment.
>
> [snip]
>
> <!-- *** THIS IS MY CONNECTOR FOR PORT 443: COPIED FROM PAST
> TOMCAT VERSIONS *** --> <Connector port="443" protocol="HTTP/1.1"
> SSLEnabled="true" maxThreads="150" enableLookups="false"
> scheme="https" secure="true" keystoreFile="./keys/.keystore"
> keystorePass="password" clientAuth="false" sslProtocol="TLS" />
You should really read the new TLS configuration guide[1] and use
<Connector> with a nested <SSLHostConfig> element.
But there isn't anything in there that looks to be a problem to me.
My guess is that you are using a very new Java which has dropped
support the the SSLv2Hello psuedo-protocol. That's not actually an
encryption protocol, but instead is a handshake protocol which allows
some versions of TLS to be negotiated using an old-style SSHv2 "hello"
handshake.
If that's the problem then:
1. You shouldn't be able to start Tomcat or in fact make any
connections. Or maybe it's just a warning that it's not supported and
Java will throw the error and the client will re-connect using TLS
like any modern system should.
2. You should be able to fix it by either specifying:
<Connector ... sslEnabledProtocols="TLSv1.2" (and others if you want)
or
<Connector ...
<SSLHostConfig protocols="TLSv1.2" (and others if you want)
</Connector>
Hope that helps,
- -chris
[1] http://tomcat.apache.org/tomcat-8.5-doc/config/http.html#SSL_Support
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlytKisACgkQHPApP6U8
pFjHKQ//VLcYjW68DB8UO4GI+pW850aXDqEsMBsT4PsjYW+y9JY3Sl2oHghOfy3J
g1Qdi+CHPZfRnne5dNZt7Wh4jTnVyx6KLHu449pgijAAZ6t3sL3KEXzxfNd0n1MN
vcbjNjkBGWd4AQPUE5QK8vir2jgTpwUjj0/mbB+MVNrQIkBV6vAvzkF32J7N/fwc
yyarOlD0tR9K2xHWcCqNlNGhxxYqO2QmsTqbJGlthsco/RJ6YBpXC6Re4xqOj1pv
iERSQEKL/cuAmPqJel8LMHqthH9d/W/2RXGX1eAgn1CLXF1xnkiGtrKBHBWTpF4g
H0+4EpPm+VgLNzlnESzsGItiUt3v7+dlpyAVnNKH3yT8064J/MdbQ0iYMgk6KpVl
PrETBnVF8Sxc7TiE5AzuA8d4UGVP/v153ydljItRcwMJe+qD8qNWgUev9IL6gwGV
d2Xej5kc4GDBxyvdQWS13UqqGrsE//JG9UsZ+XfRL9LLgrFIlPQsdRWfWtFdUb1Z
oiaVDk+9Yf0hhmo6lZy24FcMwbb/gNcVITYNUy3nK1g1v8saJx0AQOM9p9Yb8NaY
+Pei36BSe8bqrrxhHe2yclWrio4mVP2pydLyBF+re1PHZXbYsZuf5tZn+HBZJRx9
3U8CJiOz6ZNhn1OYYA6H+po3IC6z8KXcxBBT1KdX6Q9kpfGa9Zs=
=qSRp
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org