You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "James H. H. Lampert" <ja...@touchtonecorp.com> on 2017/10/03 21:52:59 UTC
Problem: (GSKit) No compatible cipher suite available between SSL
end points.
Dear Mr. Klement, and members of the Tomcat List:
I have a series of AS/400 programs using HTTPAPI to access services
hosted by a webapp running under Tomcat.
Up until now, I've only tested this configuration with Tomcat 7, running
on a local Linux (CentOS) box, and the last time I tested it, it worked
fine.
Today, for the first time, I tried changing the HTTPAPI calls to access
essentially the same webapp, only running in Tomcat 8 on a cloud server,
in order to find any places where the calls need to be updated to keep
up with changes in the services.
And I didn't even get that far. Instead, the SSL handshake failed with
> (GSKit) No compatible cipher suite available between SSL end points.
Now what?
I mean, I know that I need to get HTTPAPI and Tomcat speaking the same
language, but where do I begin?
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problem: (GSKit) No compatible cipher suite available between
SSL end points.
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com>.
I wrote:
>> I mean, I know that I need to get HTTPAPI and Tomcat speaking the
>> same language, but where do I begin?
Christopher Schultz (Tomcat List) wrote:
> First, I would check to see what Tomcat is actually advertising.
> There are several ways to do that. One of them is to use Qualys's
> SSLLabs server test:
>
> https://www.ssllabs.com/ssltest/
Thanks, Mr. Schultz. That gives me a start.
Ok, here's what I got back.
> Protocols
> TLS 1.3 No
> TLS 1.2 Yes
> TLS 1.1 Yes
> TLS 1.0 Yes
> SSL 3 No
> SSL 2 No
> Cipher Suites
> # TLS 1.2 (server has no preference)
> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH secp521r1 (eq. 15360 bits RSA) FS 128
> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) ECDH secp521r1 (eq. 15360 bits RSA) FS 128
> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH secp521r1 (eq. 15360 bits RSA) FS 256
> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) ECDH secp521r1 (eq. 15360 bits RSA) FS 256
> # TLS 1.1 (server has no preference)
> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH secp521r1 (eq. 15360 bits RSA) FS 128
> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH secp521r1 (eq. 15360 bits RSA) FS 256
> # TLS 1.0 (server has no preference)
> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH secp521r1 (eq. 15360 bits RSA) FS 128
> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH secp521r1 (eq. 15360 bits RSA) FS 256
I may have known how to determine what HTTPAPI supports, but if so, I've
forgotten. Ditto for adding protocols to Tomcat.
As to the client end, it's using HTTPAPI 1.24, running on an AS/400
that's at V6R1.
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: [OT] Problem: (GSKit) No compatible cipher suite available
between SSL end points.
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
James,
On 10/4/17 12:54 PM, James H. H. Lampert wrote:
> On the HTTPAPI/FTPAPI list, I was told that HTTPAPI uses the
> operating system's SSL support (which was how I thought it worked),
> and directed to look through the system values to see what it
> supports. What I found was:
>
> QSSLPCL *SEC Secure sockets layer protocols
>> *OPSYS
> (which I'm pretty sure means that all OS-supported protocols are
> available; they can also be individually specified as any or all
> of *TLSV1, *SSLV3, and *SSLV2)
>
> QSSLCSL *SEC Secure sockets layer cipher specification
> list
>> *RSA_AES_128_CBC_SHA *RSA_RC4_128_SHA *RSA_RC4_128_MD5
>> *RSA_AES_256_CBC_SHA *RSA_3DES_EDE_CBC_SHA *RSA_DES_CBC_SHA
>> *RSA_EXPORT_RC4_40_MD5 *RSA_EXPORT_RC2_CBC_40_MD5 *RSA_NULL_SHA
>> *RSA_NULL_MD5
>
> and unfortunately, IBM doesn't backport new cipher suites to older
> OS releases.
Unfortunately, these ciphers suites should no longer be used for
several reasons:
>> *RSA_RC4_128_SHA *RSA_RC4_128_MD5
Use RC4 bulk cipher algorithm, which is known[1] to be weak.
>> *RSA_EXPORT_RC4_40_MD5 *RSA_EXPORT_RC2_CBC_40_MD5
Export-grade encryption. No better than rot13[2].
>> *RSA_NULL_SHA *RSA_NULL_MD5
rot26! Twice as good!
>> *RSA_DES_CBC_SHA
Hideously outdated. I'm sorry, I don't have a reference for this one,
but...
>> *RSA_3DES_EDE_CBC_SHA
3DES (triple DES... literally DES(DES(DES(message)))) is considered
weak[3], so... single-DES is weak(weak(weak(encryption))).
>> *RSA_AES_128_CBC_SHA *RSA_AES_256_CBC_SHA
Sadly, these remaining cipher suites use CBC mode which is also
weak[4] when used with TLSv1 and earlier. Using TLSv1.2 mitigates
these issues. Use of GCM would be better if you can use them. If this
is all the client supports, then that's what you'll have to live with.
But *definitely* disable all the other algorithms if you care even a
little bit about your traffic.
Are you able to use any other kind of client?
Hope that helps,
- -chris
[1]
https://blog.qualys.com/ssllabs/2013/03/19/rc4-in-tls-is-broken-now-what
[2]
https://nakedsecurity.sophos.com/2015/03/04/the-freak-bug-in-tlsssl-what
- -you-need-to-know/
[3]
https://community.qualys.com/thread/16555-triple-des-is-bad-now-sweet-32
- -cve-2016-2183-cve-2016-6329
[4] https://blog.qualys.com/ssllabs/2014/12/08/poodle-bites-tls (CBC=wea
k)
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlnVRNwdHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFhWkRAAkSaTqa3OPol82FGw
6LSkLouidyLWyry/WC60h326qbKZoVCoviCfkgRNQAd4lqqiClAncAW1Wl9/4V3d
ijBCI/zDHzGXnsIzG8bQ5cz17FWSQIIWx02nb9VYha3t5MUGes3LHw3EStK/mKWU
6PcX50rm6XJssyUJLLvxKttRtBmEwXfJ1iklRvYhk2P5a35Sq4jp3hO3asZQ7S/L
xAuBTX3vVl0HI2Zonl8486vdNrj/sEFow8DgudfJ86zXh2eLjLOgQhsL2V1ly2+U
ButFwpTjqJTsrWIJcCdqJkJqeHm7oakPt9oVAr2tnltBz1Lxh23eXxTc4IxYTH/g
0IYywgcDdXlWF3T0aT50/sO8c/G3FiyaRvw0Q4q5Ifu9yq75EdGf8WgvXSH9iZYJ
Xh+ozw2wIOTBTcthf+QKQJ5boNjD88f9IyW5PG09ZS3NiSR5BrHDI5dZNuflQ4u/
uVILyZVmNl30MotfJP8FtaWO5VBtnZvh674QmgVpg5IUFMkGo1fIHjBy3NfQaRLt
fW5GvMemGAfATjFh6ElrkmKb6Whkz6qi27+OIZzpGHumN+ZJ7t5u9wy41UMgUqPl
UTJmTUko9vlQkxCtcOrNcWVPAtzFRVBMYROyvUMb1ePwGugeiF36UEtybqjKVR8Z
LEK/qYLdjWFBTc2JqkPBnlslSe4=
=KGQL
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: BREAKTHROUGH (but not solved) Re: Problem: (GSKit) No compatible
cipher suite available between SSL end points.
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com>.
On 10/9/17, 2:19 PM, Christopher Schultz (Tomcat List guru) wrote (with
regard to a "ciphers" clause in a connector tag):
. . .
> You need to list everything.
. . .
Ok. I really didn't need a command-line tool (thanks, though, on behalf
of whoever actually does end up needing one); just an example, and I
found one at https://tinyurl.com/y9aqpkvm
Based on that example, I then pulled up the "Configured ciphers per
connector" page on the TC 8.5 server, and copied and pasted all of them
into a new ciphers clause on my connector tag, and then copied and
pasted TLS_RSA_WITH_AES_256_CBC_SHA in at the end, from a copy of the
SSLInfo output. After restarting Tomcat, "TLS_RSA_WITH_AES_256_CBC_SHA"
appeared in the "Configured ciphers" page, and the AS/400 was able to
access the server.
Thanks, Messrs. Schultz, Kreuser, Thomas of the Tomcat List, and Messrs
Stone and Klement of the HTTPAPI List.
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: BREAKTHROUGH (but not solved) Re: Problem: (GSKit) No compatible
cipher suite available between SSL end points.
Posted by "Terence M. Bandoian" <te...@tmbsw.com>.
On 10/10/2017 1:20 AM, Peter Kreuser wrote:
> Christopher,
>
> A good read on the appropriate (openssl) cipher string that I use can be found here:
> https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/
> Hynek explains the whys and don'ts and updates the string on a regular basis!
>
> HTH
>
> Peter
Nice article. Thanks!
-Terence Bandoian
http://www.tmbsw.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: BREAKTHROUGH (but not solved) Re: Problem: (GSKit) No compatible cipher suite available between SSL end points.
Posted by Peter Kreuser <lo...@kreuser.name>.
Christopher,
Peter Kreuser
> Am 10.10.2017 um 00:14 schrieb Christopher Schultz <ch...@christopherschultz.net>:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> James,
>
>> On 10/9/17 5:19 PM, Christopher Schultz wrote:
>>> On 10/6/17 6:34 PM, James H. H. Lampert wrote:
>>> Noting that my connector tag is written using Tomcat 7 connector
>>> syntax, is there a good example of how to code a ciphers clause
>>> for that tag?
>>
>> Tomcat 8.5+ and 9.0+ can do it... but nobody has written a
>> command-line tool around that capability. (I could have sworn such
>> a tool existed already. I guess I'll write one.)
>
> Okay, it's in Tomcat 9, now. Grab Tomcat 9 trunk, build it ("ant
> deploy"), then run:
>
> $ output/build/bin/ciphers.sh [cipherspec]
>
> where "cipherspec" is an OpenSSL-style cipher suite spec, like:
>
> $ output/build/bin/ciphers.sh 'DEFAULT'
>
> This gives you the JVM's current default, and dumps-out all of the
> IANA-style cipher suite names. So if you want to add one cipher suite
> to the default Java suites, just do this:
>
> $ output/build/bin/ciphers.sh 'DEFAULT'
>
> and then add this to the end:
>
> TLS_RSA_WITH_AES_256_CBC_SHA
>
> (Unless TLS_RSA_WITH_AES_256_CBC_SHA is already present in the list.)
>
> Note that the "DEFAULT" list has a bunch of junk you don't need.
> Specifically, you can probably get rid of all of these things with no
> ill effects, and your configuration will "look" simpler:
>
> $ ./bin/ciphers.sh '!PSK:!aNULL:!DSA:!SRP:!DSS:HIGH'
A good read on the appropriate (openssl) cipher string that I use can be found here:
https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/
Hynek explains the whys and don'ts and updates the string on a regular basis!
HTH
Peter
> Hope that helps,
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlnb9NkdHGNocmlzQGNo
> cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFisoA//bj9GFzlMaZdPYXHt
> y2iQIToESUg6Wa8vU5lQscLDfqtXeAIawiXusILz/th1fCu1usy8HeC/5nBINXAQ
> McbEUSRiq6YitPXDIwXqbOGZS76vxmheFPTst6gHCN6hNOYbFEbejK3cxX8s0Bbg
> kXtqcrnnN+a+J5UZmFeB3tctQfwsVLyGcvcwzDRTjFCIjrD1CwdEd+Ckk740jCFU
> HXgEewO6rVnxAx80hP2c9ztsHblNt0KFm4zMtWjxmHTigac1EEA1ZAi5P3nIJu5n
> 7HIw0jVX3qZHamVHXWSPb7skEZY/wj7Kko8XmJFWS0bbwuaTQJ+Pr8ZJPT145/Tb
> F0w6PqPqiR9sre7Yvy4v9y/QOqFjujEqMzkTNedRaBEItmzELPkYBBms2b2bkIVj
> bMptV5FidCthzvJAnQ5efuiG9qYCuHajNEjQM4Mhu0t95yolmh4+yD2yxA4sS35W
> YPxy24tgY9A2nNpJS+QSWtCzkQBJz+0Uxnw8y3AbW2oRkA649i+9+KppSAqCx7kH
> QYUSwTD+7aETlVthfANEr5D/MbzJbflhTjXl/bZjuEc2p1tWPxZrqC+E8FwniMLL
> NYwK4rMDrSZfrgY7mn6uPcTxzEIMTj/KvtaZCFY1GRAlAf16vNVlnCHQzMvlYKGW
> gtqS2tF9DBurCs65qocxtWLAQwU=
> =bEIh
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Re: BREAKTHROUGH (but not solved) Re: Problem: (GSKit) No compatible
cipher suite available between SSL end points.
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
James,
On 10/9/17 5:19 PM, Christopher Schultz wrote:
> On 10/6/17 6:34 PM, James H. H. Lampert wrote:
>> Noting that my connector tag is written using Tomcat 7 connector
>> syntax, is there a good example of how to code a ciphers clause
>> for that tag?
>
> Tomcat 8.5+ and 9.0+ can do it... but nobody has written a
> command-line tool around that capability. (I could have sworn such
> a tool existed already. I guess I'll write one.)
Okay, it's in Tomcat 9, now. Grab Tomcat 9 trunk, build it ("ant
deploy"), then run:
$ output/build/bin/ciphers.sh [cipherspec]
where "cipherspec" is an OpenSSL-style cipher suite spec, like:
$ output/build/bin/ciphers.sh 'DEFAULT'
This gives you the JVM's current default, and dumps-out all of the
IANA-style cipher suite names. So if you want to add one cipher suite
to the default Java suites, just do this:
$ output/build/bin/ciphers.sh 'DEFAULT'
and then add this to the end:
TLS_RSA_WITH_AES_256_CBC_SHA
(Unless TLS_RSA_WITH_AES_256_CBC_SHA is already present in the list.)
Note that the "DEFAULT" list has a bunch of junk you don't need.
Specifically, you can probably get rid of all of these things with no
ill effects, and your configuration will "look" simpler:
$ ./bin/ciphers.sh '!PSK:!aNULL:!DSA:!SRP:!DSS:HIGH'
Hope that helps,
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlnb9NkdHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFisoA//bj9GFzlMaZdPYXHt
y2iQIToESUg6Wa8vU5lQscLDfqtXeAIawiXusILz/th1fCu1usy8HeC/5nBINXAQ
McbEUSRiq6YitPXDIwXqbOGZS76vxmheFPTst6gHCN6hNOYbFEbejK3cxX8s0Bbg
kXtqcrnnN+a+J5UZmFeB3tctQfwsVLyGcvcwzDRTjFCIjrD1CwdEd+Ckk740jCFU
HXgEewO6rVnxAx80hP2c9ztsHblNt0KFm4zMtWjxmHTigac1EEA1ZAi5P3nIJu5n
7HIw0jVX3qZHamVHXWSPb7skEZY/wj7Kko8XmJFWS0bbwuaTQJ+Pr8ZJPT145/Tb
F0w6PqPqiR9sre7Yvy4v9y/QOqFjujEqMzkTNedRaBEItmzELPkYBBms2b2bkIVj
bMptV5FidCthzvJAnQ5efuiG9qYCuHajNEjQM4Mhu0t95yolmh4+yD2yxA4sS35W
YPxy24tgY9A2nNpJS+QSWtCzkQBJz+0Uxnw8y3AbW2oRkA649i+9+KppSAqCx7kH
QYUSwTD+7aETlVthfANEr5D/MbzJbflhTjXl/bZjuEc2p1tWPxZrqC+E8FwniMLL
NYwK4rMDrSZfrgY7mn6uPcTxzEIMTj/KvtaZCFY1GRAlAf16vNVlnCHQzMvlYKGW
gtqS2tF9DBurCs65qocxtWLAQwU=
=bEIh
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: BREAKTHROUGH (but not solved) Re: Problem: (GSKit) No compatible
cipher suite available between SSL end points.
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
James,
On 10/6/17 6:34 PM, James H. H. Lampert wrote:
> On 10/6/17, 6:58 AM, Mark Thomas (Tomcat List) wrote:
>
>> It might help to think of it like this:
>>
>> There are the ciphers that a JVM supports. The JVM only enables
>> sub-set of the supported ciphers are enabled by default. Tomcat
>> with a default configuration only uses a sub-set of the ciphers
>> that the JVM enables by default. . . . It looks like you have an
>> incompatible set of ciphers configured.
>>
>> As per Chris's previous email, it looks like RSA_AES_256_CBC_SHA
>> is the least worse option. The Java name for this is:
>> TLS_RSA_WITH_AES_256_CBC_SHA
>
> I should have tried this DAYS ago. There is also a Tomcat 7 server
> installed on the Google Cloud server. With no apparent differences
> in the Java list of available and "enabled-by-default" ciphers
> between the two boxes, it's clear that the biggest single
> difference that I'm actually able to do anything about is which
> Tomcat server is running on 443.
>
> So with both Tomcat servers shut down, I switched Tomcat 7 over to
> port 443, brought it up, and tried connecting to it from the same
> program as before.
>
> This time, I got a 404. Not the least bit surprising, since the
> webapp context isn't actually installed on the Tomcat 7 server.
>
> Incidentally, I also tried running the ssllabs.com test on the
> Tomcat 7 server. The results weren't very meaningful: it only
> listed the ECDHE suites, but then again, it only listed the ECDHE
> suites when I tried it on one of our other Tomcat 7 servers.
>
>> Tomcat with a default configuration only uses a sub-set of the
>> ciphers that the JVM enables by default.
>
> So is there a way, short of downloading and recompiling Tomcat
> myself, to control what's in that default subset of a default
> subset?
Nope. You can't change the JVM (well, you CAN but it's not worth it)
and you can't change Tomcat's further-restricted list of cipher
suites. But it's got nearly everything you'd actually want in there,
and it's even got some stuff you might actually NOT want in there,
depending upon your level of paranoia.
> Or failing that, is there a way, in my connector tag, to specify
> "Use TLS_RSA_WITH_AES_256_CBC_SHA in addition to all the suites
> Tomcat 8.5 uses by default"?
No.
> Or do I need to list all the Tomcat 8.5 defaults in a "ciphers"
> clause, along with the TLS_RSA_WITH_AES_256_CBC_SHA?
You need to list everything.
> Noting that my connector tag is written using Tomcat 7 connector
> syntax, is there a good example of how to code a ciphers clause for
> that tag?
Tomcat 8.5+ and 9.0+ can do it... but nobody has written a
command-line tool around that capability. (I could have sworn such a
tool existed already. I guess I'll write one.)
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlnb5/AdHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFh7nA/+Nq5pXhaL9++l2y8b
LSVfaoy5PamsIFvn5paEchot2XfvoE4TXMWb3e5EmVPPk89QLZKn/jMzOukKs/9S
7g4QVtngxEfi9W48poj45abfwMk+Rh2Na4fNIwMLjNFFVYLH1AeuO/hvDk1/Zf0z
mIgqa85OlMuwnpWF3AqWI/KEOi9d9PNOIm2TT8c+lI6WyR99M+FTWtt10Zlv/IFG
7JeSEbKURxkacOlwe6aR7Paa7Wt2LcUldYcAhmYwKJPvHJaYcs1ZdbvPsx2h8j2E
eGBftxjl9+2cx0+5+tkQtl0nAotZmqoX3SsIgeDJWwUdUI/7iLkJMt/d8A1gdGgR
AaCZgW09fn8MpzAaqqOz+FdqpNcldBsiut4o4gv+bUhDQClijvpz/LDKW02eJhEi
6/1U+Eqe5MyXj+zn02Am+z7uoyyU8H1F3QUEN1+OsKH3/AsOCZBwkqeBvig3a8Mb
XXPCOUroDqW4zhvAd8/mk0tuoo2OZ+O3rd/VuZecDU7uuhclvgp7+orhsIwrDL0o
jynVbIm0k2VPHPwDQRAL9scdXc0BGFih8D6tP9JBmIgVHQhHVoqbJkwfo+Zrer/L
cLP7R2iBcg2d2EqYxlMXYmgVf4jnVcGTfn1n2V9Hc6YYhcLIxTF3s37xln2StERB
69veYEnl/qoqo/7IcKp5YrE+kP8=
=w1+P
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: BREAKTHROUGH (but not solved) Re: Problem: (GSKit) No compatible
cipher suite available between SSL end points.
Posted by lo...@kreuser.name.
James,
> On 10/6/17, 6:58 AM, Mark Thomas (Tomcat List) wrote:
>
>> It might help to think of it like this:
>>
>> There are the ciphers that a JVM supports.
>> The JVM only enables sub-set of the supported ciphers are enabled by
>> default.
>> Tomcat with a default configuration only uses a sub-set of the ciphers
>> that the JVM enables by default.
>> . . .
>> It looks like you have an incompatible set of ciphers configured.
>>
>> As per Chris's previous email, it looks like RSA_AES_256_CBC_SHA is the
>> least worse option. The Java name for this is:
>> TLS_RSA_WITH_AES_256_CBC_SHA
>
> I should have tried this DAYS ago. There is also a Tomcat 7 server installed on the Google Cloud server. With no apparent differences in the Java list of available and "enabled-by-default" ciphers between the two boxes, it's clear that the biggest single difference that I'm actually able to do anything about is which Tomcat server is running on 443.
>
> So with both Tomcat servers shut down, I switched Tomcat 7 over to port 443, brought it up, and tried connecting to it from the same program as before.
>
> This time, I got a 404. Not the least bit surprising, since the webapp context isn't actually installed on the Tomcat 7 server.
>
> Incidentally, I also tried running the ssllabs.com <http://ssllabs.com/> test on the Tomcat 7 server. The results weren't very meaningful: it only listed the ECDHE suites, but then again, it only listed the ECDHE suites when I tried it on one of our other Tomcat 7 servers.
>
> > Tomcat with a default configuration only uses a sub-set of the ciphers
> > that the JVM enables by default.
>
> So is there a way, short of downloading and recompiling Tomcat myself, to control what's in that default subset of a default subset?
>
> Or failing that, is there a way, in my connector tag, to specify "Use TLS_RSA_WITH_AES_256_CBC_SHA in addition to all the suites Tomcat 8.5 uses by default"?
>
> Or do I need to list all the Tomcat 8.5 defaults in a "ciphers" clause, along with the TLS_RSA_WITH_AES_256_CBC_SHA?
>
> Noting that my connector tag is written using Tomcat 7 connector syntax, is there a good example of how to code a ciphers clause for that tag?
>
> --
> JHHL
>
Apparently Tomcat 7 syntax will not support openssl syntax like HIGH:+AES256:!MD5:... That will perfectly work with Tomcat 8.5 with the new ssl syntax, and that is a major achievement.
A quick dig into tomcat7 conf and tested with docker will lead you to the following working ssl conf. Be aware that Java7 is not really able to handle modern ssl requirements like bit length > 1024bit or server cipher order.
<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150" SSLEnabled="true" scheme="https" secure="true" ciphers="TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA"
clientAuth=“false" sslProtocol="TLS" keystoreFile="${catalina.base}/conf/ssl/jssecacerts4" keystorePass="changeit" />
You may want to test a local ssl setup with the great testssl.sh tool by dirk wetter (https://testssl.sh <https://testssl.sh/>), also available on docker.
I’ve picked the ciphers from the list that testssl.sh showed me for the standard conf of Tomcat 8.0.47 and JRE7 (RFC notation). Then I’ve added your requested cipher.
HTH,
Peter
BREAKTHROUGH (but not solved) Re: Problem: (GSKit) No compatible
cipher suite available between SSL end points.
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com>.
On 10/6/17, 6:58 AM, Mark Thomas (Tomcat List) wrote:
> It might help to think of it like this:
>
> There are the ciphers that a JVM supports.
> The JVM only enables sub-set of the supported ciphers are enabled by
> default.
> Tomcat with a default configuration only uses a sub-set of the ciphers
> that the JVM enables by default.
> . . .
> It looks like you have an incompatible set of ciphers configured.
>
> As per Chris's previous email, it looks like RSA_AES_256_CBC_SHA is the
> least worse option. The Java name for this is:
> TLS_RSA_WITH_AES_256_CBC_SHA
I should have tried this DAYS ago. There is also a Tomcat 7 server
installed on the Google Cloud server. With no apparent differences in
the Java list of available and "enabled-by-default" ciphers between the
two boxes, it's clear that the biggest single difference that I'm
actually able to do anything about is which Tomcat server is running on 443.
So with both Tomcat servers shut down, I switched Tomcat 7 over to port
443, brought it up, and tried connecting to it from the same program as
before.
This time, I got a 404. Not the least bit surprising, since the webapp
context isn't actually installed on the Tomcat 7 server.
Incidentally, I also tried running the ssllabs.com test on the Tomcat 7
server. The results weren't very meaningful: it only listed the ECDHE
suites, but then again, it only listed the ECDHE suites when I tried it
on one of our other Tomcat 7 servers.
> Tomcat with a default configuration only uses a sub-set of the ciphers
> that the JVM enables by default.
So is there a way, short of downloading and recompiling Tomcat myself,
to control what's in that default subset of a default subset?
Or failing that, is there a way, in my connector tag, to specify "Use
TLS_RSA_WITH_AES_256_CBC_SHA in addition to all the suites Tomcat 8.5
uses by default"?
Or do I need to list all the Tomcat 8.5 defaults in a "ciphers" clause,
along with the TLS_RSA_WITH_AES_256_CBC_SHA?
Noting that my connector tag is written using Tomcat 7 connector syntax,
is there a good example of how to code a ciphers clause for that tag?
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problem: (GSKit) No compatible cipher suite available between SSL
end points.
Posted by Mark Thomas <ma...@apache.org>.
On 05/10/17 18:52, James H. H. Lampert wrote:
> This just keeps getting weirder.
>
> Late yesterday afternoon, I did a lengthy "stare-and-compare" between
> what SSLInfo returned for the two different Tomcat servers, and I
> couldn't find any differences. But then, I got called away from this on
> something that kept me in the office until after 7 PM.
>
> Finally getting back to it, I looked at the "connector ciphers" on the
> Tomcat 8 manager (there isn't one on the Tomcat 7 manager), and saw that
> only 16 of the 36 ciphers that SSLInfo starred as "default" are actually
> enabled in Tomcat.
It might help to think of it like this:
There are the ciphers that a JVM supports.
The JVM only enables sub-set of the supported ciphers are enabled by
default.
Tomcat with a default configuration only uses a sub-set of the ciphers
that the JVM enables by default.
This is a little dated but might help:
https://wiki.apache.org/tomcat/Security/Ciphers
> Then, using what Mr. Schultz told me about reading cipher names, I
> compared what actually *does* come up in the Tomcat 8 manager with the
> DSPSYSVAL on the AS/400. And I found that if
>> *RSA_AES_256_CBC_SHA
> is the same as
>> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
>
> then maybe we DO have a common cipher, at least in theory (unless
> "ECDHE" makes it otherwise).
ECDHE makes them different.
> Unfortunately, I can't run the local box's Tomcat server through
> SSLLabs, because it's on a nonstandard port number, and Tomcat 7 doesn't
> have a "connector ciphers" button on the manager main page.
>
> The cloud box is a Google Compute Engine instance. Is it possible that
> Google is somehow vetoing the handshake?
It looks like you have an incompatible set of ciphers configured.
As per Chris's previous email, it looks like RSA_AES_256_CBC_SHA is the
least worse option. The Java name for this is:
TLS_RSA_WITH_AES_256_CBC_SHA
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problem: (GSKit) No compatible cipher suite available between
SSL end points.
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com>.
This just keeps getting weirder.
Late yesterday afternoon, I did a lengthy "stare-and-compare" between
what SSLInfo returned for the two different Tomcat servers, and I
couldn't find any differences. But then, I got called away from this on
something that kept me in the office until after 7 PM.
Finally getting back to it, I looked at the "connector ciphers" on the
Tomcat 8 manager (there isn't one on the Tomcat 7 manager), and saw that
only 16 of the 36 ciphers that SSLInfo starred as "default" are actually
enabled in Tomcat.
Then, using what Mr. Schultz told me about reading cipher names, I
compared what actually *does* come up in the Tomcat 8 manager with the
DSPSYSVAL on the AS/400. And I found that if
> *RSA_AES_256_CBC_SHA
is the same as
> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
then maybe we DO have a common cipher, at least in theory (unless
"ECDHE" makes it otherwise).
Unfortunately, I can't run the local box's Tomcat server through
SSLLabs, because it's on a nonstandard port number, and Tomcat 7 doesn't
have a "connector ciphers" button on the manager main page.
The cloud box is a Google Compute Engine instance. Is it possible that
Google is somehow vetoing the handshake?
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problem: (GSKit) No compatible cipher suite available between SSL
end points.
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
James,
On 10/4/17 3:44 PM, James H. H. Lampert wrote:
> On 10/4/17, 12:26 PM, Christopher Schultz wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>>
>> James,
> . . .
>> Okay so you are in no way interfering with the defaults. That
>> means you'll get (depending upon your exact versions of various
>> things) a Tomcat which supports TLSv1 or later, and most of the
>> cipher suites that are shown as "default" above.
>>
>> Your choice of TLS certificate may affect some of the things that
>> you can do, but I see that you've got an RSA certificate from the
>> output from SSLLabs, so you shouldn't have any problems with a
>> DSS certificate or anything like that. (Use of DSS certs these
>> days is fairly rare).
> . . .
>> Strange. I would have expected Tomcat to enable more cipher
>> suites with a default configuration given the SSLInfo output
>> above.
>>
>> Are you sure you are using the same Java version with Tomcat as
>> you did to run those commands above?
>
> Dear Mr. Schultz:
"Chris" is fine. We're all friends, here.
> It sure looks like the same Java version. Here is what the manager
> returns:
>> Apache Tomcat/8.5.14 (Debian) 1.7.0_151-b01 Oracle Corporation
>> Linux 3.16.0-4-amd64 amd64
>
> It would definitely be helpful if the OS/400 names of the cipher
> suites more precisely matched the Java names. To recap, the QSSLCSL
> system value on the AS/400 shows (using the OS/400 naming
> conventions)
>> *RSA_AES_128_CBC_SHA *RSA_RC4_128_SHA *RSA_RC4_128_MD5
>> *RSA_AES_256_CBC_SHA *RSA_3DES_EDE_CBC_SHA *RSA_DES_CBC_SHA
>> *RSA_EXPORT_RC4_40_MD5 *RSA_EXPORT_RC2_CBC_40_MD5 *RSA_NULL_SHA
>> *RSA_NULL_MD5
If you know how to "read" cipher suite descriptions, the differences
don't matter much. They are all made-up of the following components:
1. protocol (not shown in OpenSSL-style names, like those above)
2. authentication algorithm (usually RSA, ECDH, or ECDHE)
3. bulk (symmetric) cipher algorithm (e.g. RC4, AES-128, 3DES, Camellia)
This includes the "block cipher mode e.g. CBC, GCM, etc.)
4. signature algorithm (e.g. MD5, SHA, etc.)
The differences between the cipher suite names in different tools
comes down to how expressive they are. For example, Java says "SSL_"
or "TLS_" before every cipher, but that's largely useless. Some names
in different dialects show different levels of detail about the
underlying algorithms, or are more readable.
Take this one for example. Java (and SSLLabs) calls it
"TLS_RSA_WITH_AES_128_CBC_SHA" but the same algorithm is called
"RSA_AES_128_CBC_SHA" by OpenSSL and similar tools. It's all still in
there.. it's just that OpenSSL doesn't bother with the "TLS_" prefix
and the "_WITH_" embedded in the middle.
When it all comes down to it, the TLS (nee SSL) spec defines certain
cipher suites by "cipher id" which is a numeric, explicitly-defined
set of crypto primitives combined into a "cipher suite", which will be
negotiated by the client and server when they perform their initial
handshake.
You can read all the gory details here[1]. For example, the
aforementioned RSA_AES_128_CBC_SHA cipher suite is cipher 0x00002F. It
doesn't matter what the tool calls it; cipher 0x00002f always has
those criteria. Of course, they aren't very readable.
That document is a bit out of date, but it does show you how things
were back in 2009, and makes you wonder why it took so damned long for
The World to adopt TLSv1.2.
- -chris
[1] https://www.thesprawl.org/research/tls-and-ssl-cipher-suites/
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlnVR4odHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFiQORAAsV9+BFL06kve1kCU
y42ojIStrzWvoE8yKxVxjfTL1DuaGiLMtmiS+/QfeJWL2E5lWCbolA2i+BDJ5wQB
4MH7iVBbKpRxodyDUuoVI9IE3zuYYxe8bQnVbyfkCl8a1WPGTjAURqFTQHJ3UqI4
CGN1LzQrvVBzJ6WjMu8tOTjm5758pJhI3kwfJ/NSw6gOXguhwMC9uTtxhzhBm1TE
+vIOCccuqjpo/tAZRBK6OPtBHA5yydQjk+vEpUdvurV+vLlSkV+7bpmymWVZtJKF
4XaDuCglKeHYut2/CcEW3+D2JuCjHH6FD08Qp/ft4NiDNG8gPfrO4KBaXd+dQ6Hq
DF6/fvcTQacXpyuPJ5FShXjgd9hweBD4GC1D4pzkdfXtMUtBzlB6PzDNd72Tqq6w
Uf3fgfiVnEZ6ObMonGyX7LcxCRh3yWVA/WzgexBbFxk3WNkvM6/vcbk4+CfPuPuF
sVnw8OzmxeT5nmyy4oNxiAxM93W0CTxA3yPEN/ETSwKvgVlmWyCfmtP1+lq20OZh
JedWCjG4+QmCWk4U1RdKWnl0Dxzk0vTAkrT7REGf084pDc4JiZUjA5/FJgdvq7V6
nDFrkVmXnOaCtk3L0p0NVEodXlqSdOaO/6qF+MqNLIKAdNRgDqRAI4gggM4GlBhf
kYqj6DPpSrNxGE0jd0Eub3dB3RA=
=iFq6
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problem: (GSKit) No compatible cipher suite available between
SSL end points.
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com>.
On 10/4/17, 12:26 PM, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> James,
. . .
> Okay so you are in no way interfering with the defaults. That means
> you'll get (depending upon your exact versions of various things) a
> Tomcat which supports TLSv1 or later, and most of the cipher suites
> that are shown as "default" above.
>
> Your choice of TLS certificate may affect some of the things that you
> can do, but I see that you've got an RSA certificate from the output
> from SSLLabs, so you shouldn't have any problems with a DSS
> certificate or anything like that. (Use of DSS certs these days is
> fairly rare).
. . .
> Strange. I would have expected Tomcat to enable more cipher suites
> with a default configuration given the SSLInfo output above.
>
> Are you sure you are using the same Java version with Tomcat as you
> did to run those commands above?
Dear Mr. Schultz:
It sure looks like the same Java version. Here is what the manager returns:
> Apache Tomcat/8.5.14 (Debian) 1.7.0_151-b01 Oracle Corporation Linux 3.16.0-4-amd64 amd64
It would definitely be helpful if the OS/400 names of the cipher suites
more precisely matched the Java names. To recap, the QSSLCSL system
value on the AS/400 shows (using the OS/400 naming conventions)
> *RSA_AES_128_CBC_SHA
> *RSA_RC4_128_SHA
> *RSA_RC4_128_MD5
> *RSA_AES_256_CBC_SHA
> *RSA_3DES_EDE_CBC_SHA
> *RSA_DES_CBC_SHA
> *RSA_EXPORT_RC4_40_MD5
> *RSA_EXPORT_RC2_CBC_40_MD5
> *RSA_NULL_SHA
> *RSA_NULL_MD5
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problem: (GSKit) No compatible cipher suite available between SSL
end points.
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
James,
On 10/4/17 3:15 PM, James H. H. Lampert wrote:
> Christopher Schultz (Tomcat list guru) wrote:
/me bows
>> Looks like your server only has ECDHE-based suites available, and
>> the client supports none of those. Can you post your <Connector>
>> configuration from conf/server.xml?
>
> Yes, and I can also post something else.
>
> I found the Java source for your own "SSLInfo" program (yes, I
> actually do attempt to pursue any line of research that occurs to
> me, even as I'm begging for help), compiled it, and put it onto
> both the local box where the AS/400 is able to connect to the
> Tomcat server, and on the cloud server where it isn't.
>
> On the local box, running Tomcat 7, I get:
>> java -showversion SSLInfo java version "1.7.0_131" OpenJDK
>> Runtime Environment (IcedTea 2.6.9) (7u131-2.6.9-2~deb8u1)
>> OpenJDK Client VM (build 24.131-b00, mixed mode, sharing)
>>
>> Default Cipher SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA *
>> SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA SSL_DHE_DSS_WITH_DES_CBC_SHA
>> SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA *
>> SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA SSL_DHE_RSA_WITH_DES_CBC_SHA
>> SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA
>> SSL_DH_anon_EXPORT_WITH_RC4_40_MD5
>> SSL_DH_anon_WITH_3DES_EDE_CBC_SHA SSL_DH_anon_WITH_DES_CBC_SHA
>> SSL_DH_anon_WITH_RC4_128_MD5 SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
>> SSL_RSA_EXPORT_WITH_RC4_40_MD5 *
>> SSL_RSA_WITH_3DES_EDE_CBC_SHA SSL_RSA_WITH_DES_CBC_SHA
>> SSL_RSA_WITH_NULL_MD5 SSL_RSA_WITH_NULL_SHA
>> SSL_RSA_WITH_RC4_128_MD5 SSL_RSA_WITH_RC4_128_SHA *
>> TLS_DHE_DSS_WITH_AES_128_CBC_SHA *
>> TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 *
>> TLS_DHE_DSS_WITH_AES_256_CBC_SHA *
>> TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 *
>> TLS_DHE_RSA_WITH_AES_128_CBC_SHA *
>> TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 *
>> TLS_DHE_RSA_WITH_AES_256_CBC_SHA *
>> TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
>> TLS_DH_anon_WITH_AES_128_CBC_SHA
>> TLS_DH_anon_WITH_AES_128_CBC_SHA256
>> TLS_DH_anon_WITH_AES_256_CBC_SHA
>> TLS_DH_anon_WITH_AES_256_CBC_SHA256 *
>> TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA *
>> TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA *
>> TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 *
>> TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA *
>> TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
>> TLS_ECDHE_ECDSA_WITH_NULL_SHA TLS_ECDHE_ECDSA_WITH_RC4_128_SHA *
>> TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA *
>> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA *
>> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 *
>> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA *
>> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
>> TLS_ECDHE_RSA_WITH_NULL_SHA TLS_ECDHE_RSA_WITH_RC4_128_SHA *
>> TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA *
>> TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA *
>> TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 *
>> TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA *
>> TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
>> TLS_ECDH_ECDSA_WITH_NULL_SHA TLS_ECDH_ECDSA_WITH_RC4_128_SHA *
>> TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA *
>> TLS_ECDH_RSA_WITH_AES_128_CBC_SHA *
>> TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256 *
>> TLS_ECDH_RSA_WITH_AES_256_CBC_SHA *
>> TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDH_RSA_WITH_NULL_SHA
>> TLS_ECDH_RSA_WITH_RC4_128_SHA
>> TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA
>> TLS_ECDH_anon_WITH_AES_128_CBC_SHA
>> TLS_ECDH_anon_WITH_AES_256_CBC_SHA TLS_ECDH_anon_WITH_NULL_SHA
>> TLS_ECDH_anon_WITH_RC4_128_SHA *
>> TLS_EMPTY_RENEGOTIATION_INFO_SCSV
>> TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5
>> TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA
>> TLS_KRB5_EXPORT_WITH_RC4_40_MD5 TLS_KRB5_EXPORT_WITH_RC4_40_SHA
>> TLS_KRB5_WITH_3DES_EDE_CBC_MD5 TLS_KRB5_WITH_3DES_EDE_CBC_SHA
>> TLS_KRB5_WITH_DES_CBC_MD5 TLS_KRB5_WITH_DES_CBC_SHA
>> TLS_KRB5_WITH_RC4_128_MD5 TLS_KRB5_WITH_RC4_128_SHA *
>> TLS_RSA_WITH_AES_128_CBC_SHA *
>> TLS_RSA_WITH_AES_128_CBC_SHA256 *
>> TLS_RSA_WITH_AES_256_CBC_SHA *
>> TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_NULL_SHA256
Right. That confirms that your Tomcat 7 server supports quite a few
cipher suites, many of which are enabled by default. On that server,
you'd have to specifically disable them in order for them not to work.
(Some of them might be SSLv3 cipher suites, and would be disabled
along with that protocol, but most cipher suites are for a "protocol X
or higher" kind of thing).
> and the relevant connector in server.xml (line breaks added,
> sensitive information redacted) is
>
>> <Connector port="8090"
>> protocol="org.apache.coyote.http11.Http11Protocol"
>> compression="on" compressionMinSize="2048"
>> noCompressionUserAgents="gozilla, traviata"
>> compressableMimeType="text/html,text/xml,text/plain,text/css,text/jav
ascript,text/json,
>>
>>
>>
application/x-javascript,application/javascript,application/json"
>> maxThreads="150" SSLEnabled="true" scheme="https" secure="true"
>> maxPostSize="10485760"
>> keystoreFile="/usr/share/apache-tomcat-7.0.57/$$$$$$$$$"
>> keyAlias="$$$$$$$$" clientAuth="false" sslProtocol="TLS" />
Okay so you are in no way interfering with the defaults. That means
you'll get (depending upon your exact versions of various things) a
Tomcat which supports TLSv1 or later, and most of the cipher suites
that are shown as "default" above.
Your choice of TLS certificate may affect some of the things that you
can do, but I see that you've got an RSA certificate from the output
from SSLLabs, so you shouldn't have any problems with a DSS
certificate or anything like that. (Use of DSS certs these days is
fairly rare).
> On the cloud box, running Tomcat 8, I get:
>> java -showversion SSLInfo java version "1.7.0_151" OpenJDK
>> Runtime Environment (IcedTea 2.6.11) (7u151-2.6.11-1~deb8u1)
>> OpenJDK 64-Bit Server VM (build 24.151-b01, mixed mode)
>>
>> Default Cipher SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA *
>> SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA SSL_DHE_DSS_WITH_DES_CBC_SHA
>> SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA *
>> SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA SSL_DHE_RSA_WITH_DES_CBC_SHA
>> SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA
>> SSL_DH_anon_EXPORT_WITH_RC4_40_MD5
>> SSL_DH_anon_WITH_3DES_EDE_CBC_SHA SSL_DH_anon_WITH_DES_CBC_SHA
>> SSL_DH_anon_WITH_RC4_128_MD5 SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
>> SSL_RSA_EXPORT_WITH_RC4_40_MD5 *
>> SSL_RSA_WITH_3DES_EDE_CBC_SHA SSL_RSA_WITH_DES_CBC_SHA
>> SSL_RSA_WITH_NULL_MD5 SSL_RSA_WITH_NULL_SHA
>> SSL_RSA_WITH_RC4_128_MD5 SSL_RSA_WITH_RC4_128_SHA *
>> TLS_DHE_DSS_WITH_AES_128_CBC_SHA *
>> TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 *
>> TLS_DHE_DSS_WITH_AES_256_CBC_SHA *
>> TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 *
>> TLS_DHE_RSA_WITH_AES_128_CBC_SHA *
>> TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 *
>> TLS_DHE_RSA_WITH_AES_256_CBC_SHA *
>> TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
>> TLS_DH_anon_WITH_AES_128_CBC_SHA
>> TLS_DH_anon_WITH_AES_128_CBC_SHA256
>> TLS_DH_anon_WITH_AES_256_CBC_SHA
>> TLS_DH_anon_WITH_AES_256_CBC_SHA256 *
>> TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA *
>> TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA *
>> TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 *
>> TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA *
>> TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
>> TLS_ECDHE_ECDSA_WITH_NULL_SHA TLS_ECDHE_ECDSA_WITH_RC4_128_SHA *
>> TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA *
>> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA *
>> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 *
>> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA *
>> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
>> TLS_ECDHE_RSA_WITH_NULL_SHA TLS_ECDHE_RSA_WITH_RC4_128_SHA *
>> TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA *
>> TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA *
>> TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256 *
>> TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA *
>> TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
>> TLS_ECDH_ECDSA_WITH_NULL_SHA TLS_ECDH_ECDSA_WITH_RC4_128_SHA *
>> TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA *
>> TLS_ECDH_RSA_WITH_AES_128_CBC_SHA *
>> TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256 *
>> TLS_ECDH_RSA_WITH_AES_256_CBC_SHA *
>> TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDH_RSA_WITH_NULL_SHA
>> TLS_ECDH_RSA_WITH_RC4_128_SHA
>> TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA
>> TLS_ECDH_anon_WITH_AES_128_CBC_SHA
>> TLS_ECDH_anon_WITH_AES_256_CBC_SHA TLS_ECDH_anon_WITH_NULL_SHA
>> TLS_ECDH_anon_WITH_RC4_128_SHA *
>> TLS_EMPTY_RENEGOTIATION_INFO_SCSV
>> TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5
>> TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA
>> TLS_KRB5_EXPORT_WITH_RC4_40_MD5 TLS_KRB5_EXPORT_WITH_RC4_40_SHA
>> TLS_KRB5_WITH_3DES_EDE_CBC_MD5 TLS_KRB5_WITH_3DES_EDE_CBC_SHA
>> TLS_KRB5_WITH_DES_CBC_MD5 TLS_KRB5_WITH_DES_CBC_SHA
>> TLS_KRB5_WITH_RC4_128_MD5 TLS_KRB5_WITH_RC4_128_SHA *
>> TLS_RSA_WITH_AES_128_CBC_SHA *
>> TLS_RSA_WITH_AES_128_CBC_SHA256 *
>> TLS_RSA_WITH_AES_256_CBC_SHA *
>> TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_NULL_SHA256
No surprise here, since the OpenJDK version is only a patch-level off
from the previous. I didn't look at every cipher suite, but it looks
like the same list.
> and the connector here is, with the exception of port number and
> keystore information, the same.
Strange. I would have expected Tomcat to enable more cipher suites
with a default configuration given the SSLInfo output above.
Are you sure you are using the same Java version with Tomcat as you
did to run those commands above?
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlnVNdMdHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFiA4hAApxtgwcB2Kd06fPZf
21CJbNj97kywm0cwYVqh0lq/LNvT0iJtv1PsSw6wvG1g8yMw2B9fkrE6VHnkmKpz
mRPbYQ7ukF6TRZFgZyfP/ntgTTKrJr4mGRwsxGLB6Guu0ME7TqQb8i/Y6xCZxdIQ
xA38BYfaRCWzD5XC+EC6FNZKSS/OWItRNUshN8yLiN0pghfMogCB0HQcMztIN7P1
bVt5f0PWFoYZO9/UxCClmmrWl/dGa4ORmkGmBjNWRLf14ej0uNLpSJy9ElH85ov4
askXvqB84v4uxAu8weGlOK9zK/HEqxjMrDfSSM3Un7yRKBiPIUXkTg/IE1JVMQDn
pKwlvqtMXuwggkTMyu3ixBfAV2fdb1dNNBx0ejmvjF50xfCiZfSlkw/Cp9JXFbKb
7PqrUc5sM3WLqG344TfGwWGhtQ41DNZggsn9iDwwBpcHGCRtIdftI7kUk+xPnKV1
sNEFlMb02DxaDscfcNFt6HqEy7tYXE8XXRMYRnHpP5EGNx8OPRCt+3FHW77EG4Hp
McHAqH88DyqVCzFy9eUYuJ8wYfU5N4v+t2msrqpixTbSzy7cccYC9cQWUqLQuKYS
1VAwUvfqX/sZg6jGVqVxAqi3jBMviLs8cw5MxlCtgBCZO5/7gvKo42wZ78fyojOw
xNUjYRY3XRS+Cb1RTJEOQ6K9ots=
=Zs7F
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problem: (GSKit) No compatible cipher suite available between
SSL end points.
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com>.
Christopher Schultz (Tomcat list guru) wrote:
> Looks like your server only has ECDHE-based suites available, and the
> client supports none of those. Can you post your <Connector>
> configuration from conf/server.xml?
Yes, and I can also post something else.
I found the Java source for your own "SSLInfo" program (yes, I actually
do attempt to pursue any line of research that occurs to me, even as I'm
begging for help), compiled it, and put it onto both the local box where
the AS/400 is able to connect to the Tomcat server, and on the cloud
server where it isn't.
On the local box, running Tomcat 7, I get:
> java -showversion SSLInfo
> java version "1.7.0_131"
> OpenJDK Runtime Environment (IcedTea 2.6.9) (7u131-2.6.9-2~deb8u1)
> OpenJDK Client VM (build 24.131-b00, mixed mode, sharing)
>
> Default Cipher
> SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA
> * SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA
> SSL_DHE_DSS_WITH_DES_CBC_SHA
> SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
> * SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA
> SSL_DHE_RSA_WITH_DES_CBC_SHA
> SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA
> SSL_DH_anon_EXPORT_WITH_RC4_40_MD5
> SSL_DH_anon_WITH_3DES_EDE_CBC_SHA
> SSL_DH_anon_WITH_DES_CBC_SHA
> SSL_DH_anon_WITH_RC4_128_MD5
> SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
> SSL_RSA_EXPORT_WITH_RC4_40_MD5
> * SSL_RSA_WITH_3DES_EDE_CBC_SHA
> SSL_RSA_WITH_DES_CBC_SHA
> SSL_RSA_WITH_NULL_MD5
> SSL_RSA_WITH_NULL_SHA
> SSL_RSA_WITH_RC4_128_MD5
> SSL_RSA_WITH_RC4_128_SHA
> * TLS_DHE_DSS_WITH_AES_128_CBC_SHA
> * TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
> * TLS_DHE_DSS_WITH_AES_256_CBC_SHA
> * TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
> * TLS_DHE_RSA_WITH_AES_128_CBC_SHA
> * TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
> * TLS_DHE_RSA_WITH_AES_256_CBC_SHA
> * TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
> TLS_DH_anon_WITH_AES_128_CBC_SHA
> TLS_DH_anon_WITH_AES_128_CBC_SHA256
> TLS_DH_anon_WITH_AES_256_CBC_SHA
> TLS_DH_anon_WITH_AES_256_CBC_SHA256
> * TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
> * TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
> * TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
> * TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
> * TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
> TLS_ECDHE_ECDSA_WITH_NULL_SHA
> TLS_ECDHE_ECDSA_WITH_RC4_128_SHA
> * TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
> * TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
> * TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
> * TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
> * TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
> TLS_ECDHE_RSA_WITH_NULL_SHA
> TLS_ECDHE_RSA_WITH_RC4_128_SHA
> * TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
> * TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA
> * TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
> * TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
> * TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
> TLS_ECDH_ECDSA_WITH_NULL_SHA
> TLS_ECDH_ECDSA_WITH_RC4_128_SHA
> * TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
> * TLS_ECDH_RSA_WITH_AES_128_CBC_SHA
> * TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
> * TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
> * TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
> TLS_ECDH_RSA_WITH_NULL_SHA
> TLS_ECDH_RSA_WITH_RC4_128_SHA
> TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA
> TLS_ECDH_anon_WITH_AES_128_CBC_SHA
> TLS_ECDH_anon_WITH_AES_256_CBC_SHA
> TLS_ECDH_anon_WITH_NULL_SHA
> TLS_ECDH_anon_WITH_RC4_128_SHA
> * TLS_EMPTY_RENEGOTIATION_INFO_SCSV
> TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5
> TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA
> TLS_KRB5_EXPORT_WITH_RC4_40_MD5
> TLS_KRB5_EXPORT_WITH_RC4_40_SHA
> TLS_KRB5_WITH_3DES_EDE_CBC_MD5
> TLS_KRB5_WITH_3DES_EDE_CBC_SHA
> TLS_KRB5_WITH_DES_CBC_MD5
> TLS_KRB5_WITH_DES_CBC_SHA
> TLS_KRB5_WITH_RC4_128_MD5
> TLS_KRB5_WITH_RC4_128_SHA
> * TLS_RSA_WITH_AES_128_CBC_SHA
> * TLS_RSA_WITH_AES_128_CBC_SHA256
> * TLS_RSA_WITH_AES_256_CBC_SHA
> * TLS_RSA_WITH_AES_256_CBC_SHA256
> TLS_RSA_WITH_NULL_SHA256
and the relevant connector in server.xml (line breaks added, sensitive
information redacted) is
> <Connector port="8090" protocol="org.apache.coyote.http11.Http11Protocol"
> compression="on" compressionMinSize="2048" noCompressionUserAgents="gozilla, traviata"
> compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,text/json,
> application/x-javascript,application/javascript,application/json"
> maxThreads="150" SSLEnabled="true" scheme="https" secure="true" maxPostSize="10485760"
> keystoreFile="/usr/share/apache-tomcat-7.0.57/$$$$$$$$$" keyAlias="$$$$$$$$"
> clientAuth="false" sslProtocol="TLS" />
On the cloud box, running Tomcat 8, I get:
> java -showversion SSLInfo
> java version "1.7.0_151"
> OpenJDK Runtime Environment (IcedTea 2.6.11) (7u151-2.6.11-1~deb8u1)
> OpenJDK 64-Bit Server VM (build 24.151-b01, mixed mode)
>
> Default Cipher
> SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA
> * SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA
> SSL_DHE_DSS_WITH_DES_CBC_SHA
> SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
> * SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA
> SSL_DHE_RSA_WITH_DES_CBC_SHA
> SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA
> SSL_DH_anon_EXPORT_WITH_RC4_40_MD5
> SSL_DH_anon_WITH_3DES_EDE_CBC_SHA
> SSL_DH_anon_WITH_DES_CBC_SHA
> SSL_DH_anon_WITH_RC4_128_MD5
> SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
> SSL_RSA_EXPORT_WITH_RC4_40_MD5
> * SSL_RSA_WITH_3DES_EDE_CBC_SHA
> SSL_RSA_WITH_DES_CBC_SHA
> SSL_RSA_WITH_NULL_MD5
> SSL_RSA_WITH_NULL_SHA
> SSL_RSA_WITH_RC4_128_MD5
> SSL_RSA_WITH_RC4_128_SHA
> * TLS_DHE_DSS_WITH_AES_128_CBC_SHA
> * TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
> * TLS_DHE_DSS_WITH_AES_256_CBC_SHA
> * TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
> * TLS_DHE_RSA_WITH_AES_128_CBC_SHA
> * TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
> * TLS_DHE_RSA_WITH_AES_256_CBC_SHA
> * TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
> TLS_DH_anon_WITH_AES_128_CBC_SHA
> TLS_DH_anon_WITH_AES_128_CBC_SHA256
> TLS_DH_anon_WITH_AES_256_CBC_SHA
> TLS_DH_anon_WITH_AES_256_CBC_SHA256
> * TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
> * TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
> * TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
> * TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
> * TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
> TLS_ECDHE_ECDSA_WITH_NULL_SHA
> TLS_ECDHE_ECDSA_WITH_RC4_128_SHA
> * TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
> * TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
> * TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
> * TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
> * TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
> TLS_ECDHE_RSA_WITH_NULL_SHA
> TLS_ECDHE_RSA_WITH_RC4_128_SHA
> * TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
> * TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA
> * TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
> * TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
> * TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
> TLS_ECDH_ECDSA_WITH_NULL_SHA
> TLS_ECDH_ECDSA_WITH_RC4_128_SHA
> * TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
> * TLS_ECDH_RSA_WITH_AES_128_CBC_SHA
> * TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
> * TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
> * TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
> TLS_ECDH_RSA_WITH_NULL_SHA
> TLS_ECDH_RSA_WITH_RC4_128_SHA
> TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA
> TLS_ECDH_anon_WITH_AES_128_CBC_SHA
> TLS_ECDH_anon_WITH_AES_256_CBC_SHA
> TLS_ECDH_anon_WITH_NULL_SHA
> TLS_ECDH_anon_WITH_RC4_128_SHA
> * TLS_EMPTY_RENEGOTIATION_INFO_SCSV
> TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5
> TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA
> TLS_KRB5_EXPORT_WITH_RC4_40_MD5
> TLS_KRB5_EXPORT_WITH_RC4_40_SHA
> TLS_KRB5_WITH_3DES_EDE_CBC_MD5
> TLS_KRB5_WITH_3DES_EDE_CBC_SHA
> TLS_KRB5_WITH_DES_CBC_MD5
> TLS_KRB5_WITH_DES_CBC_SHA
> TLS_KRB5_WITH_RC4_128_MD5
> TLS_KRB5_WITH_RC4_128_SHA
> * TLS_RSA_WITH_AES_128_CBC_SHA
> * TLS_RSA_WITH_AES_128_CBC_SHA256
> * TLS_RSA_WITH_AES_256_CBC_SHA
> * TLS_RSA_WITH_AES_256_CBC_SHA256
> TLS_RSA_WITH_NULL_SHA256
and the connector here is, with the exception of port number and
keystore information, the same.
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problem: (GSKit) No compatible cipher suite available between SSL
end points.
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
James,
On 10/4/17 12:54 PM, James H. H. Lampert wrote:
> I wrote:
>>> I mean, I know that I need to get HTTPAPI and Tomcat speaking
>>> the same language, but where do I begin?
> Here's what I got back when I ran the SSLLabs server test on the
> cloud server:
>
>> Protocols TLS 1.3 No TLS 1.2 Yes TLS 1.1 Yes TLS 1.0
>> Yes SSL 3 No SSL 2 No
>
>> Cipher Suites # TLS 1.2 (server has no preference)
>> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH secp521r1
>> (eq. 15360 bits RSA) FS 128
>> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) ECDH secp521r1
>> (eq. 15360 bits RSA) FS 128
>> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH secp521r1
>> (eq. 15360 bits RSA) FS 256
>> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) ECDH secp521r1
>> (eq. 15360 bits RSA) FS 256 # TLS 1.1 (server has no
>> preference) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH
>> secp521r1 (eq. 15360 bits RSA) FS 128
>> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH secp521r1
>> (eq. 15360 bits RSA) FS 256 # TLS 1.0 (server has no
>> preference) TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH
>> secp521r1 (eq. 15360 bits RSA) FS 128
>> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH secp521r1
>> (eq. 15360 bits RSA) FS 256
>
> On the HTTPAPI/FTPAPI list, I was told that HTTPAPI uses the
> operating system's SSL support (which was how I thought it worked),
> and directed to look through the system values to see what it
> supports. What I found was:
>
> QSSLPCL *SEC Secure sockets layer protocols
>> *OPSYS
> (which I'm pretty sure means that all OS-supported protocols are
> available; they can also be individually specified as any or all
> of *TLSV1, *SSLV3, and *SSLV2)
>
> QSSLCSL *SEC Secure sockets layer cipher specification
> list
>> *RSA_AES_128_CBC_SHA *RSA_RC4_128_SHA *RSA_RC4_128_MD5
>> *RSA_AES_256_CBC_SHA *RSA_3DES_EDE_CBC_SHA *RSA_DES_CBC_SHA
>> *RSA_EXPORT_RC4_40_MD5 *RSA_EXPORT_RC2_CBC_40_MD5 *RSA_NULL_SHA
>> *RSA_NULL_MD5
>
> and unfortunately, IBM doesn't backport new cipher suites to older
> OS releases.
Looks like your server only has ECDHE-based suites available, and the
client supports none of those. Can you post your <Connector>
configuration from conf/server.xml?
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlnVIfEdHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFjzgRAAjCWH+md+/fyVZn83
E6TiieaqXHOkD2CSWkgXk0nmG1+Vj2Llf6S/IYblNGeKZw+QY0tSTYVu57z5qE+Q
Hu2bf8o45xJ2QE+GZXbjkknCd+dz1TAyEAwHLAGsgbdhOUSCaeaLCNkk48kN7yoT
H0Y+KKuihHPrDsGJyErM8JUcN591UfBCFQOu44ACU0YaiSmhu6WzEDoDVKY5KitK
kdijejhT55gOkLHUDkwLLgimAEdcRpSSy4NlCitJ2GuXEglBW7mYxnz9aMTC/Pye
JYA9VQvbkPXJQZmX+509H8cXei0AVCtv3hSRW3BsQHsopzGiqy7dGznWq206omd5
5KckRzS5e7dIxyIM3Rt4zg27BDMeA4QEPvO+ADYb7OenYIVAKHi8EvqDgRwAzVYt
t+d79NZVmNl3ISc8Quau+Pjklx9ihgqQXANDQDQoaK0BK/+IGwGHANIbkDxo6WK0
o6cK1iodG0+/eKE8X9cwCIW/xt1pKuXZlKbjE3ZbUHpDWJb2vVYjBowMJ/S7foGm
OlCXeRky99JCckxztxz19glAviokzrL70DwvOSBkyMFZP6ml08byD7S6hxOi8Gk8
iw9EtCnF98fvWbFRzAp43ngBpWNDlNYTwBAqk759wPM7LHiiLejJ1jWM9iOOkw+O
2A1YRhrorJdUMXFRshZbsi9se8U=
=JfBi
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problem: (GSKit) No compatible cipher suite available between
SSL end points.
Posted by "James H. H. Lampert" <ja...@touchtonecorp.com>.
I wrote:
>> I mean, I know that I need to get HTTPAPI and Tomcat speaking the
>> same language, but where do I begin?
Here's what I got back when I ran the SSLLabs server test on the cloud
server:
> Protocols
> TLS 1.3 No
> TLS 1.2 Yes
> TLS 1.1 Yes
> TLS 1.0 Yes
> SSL 3 No
> SSL 2 No
> Cipher Suites
> # TLS 1.2 (server has no preference)
> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH secp521r1 (eq. 15360 bits RSA) FS 128
> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) ECDH secp521r1 (eq. 15360 bits RSA) FS 128
> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH secp521r1 (eq. 15360 bits RSA) FS 256
> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) ECDH secp521r1 (eq. 15360 bits RSA) FS 256
> # TLS 1.1 (server has no preference)
> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH secp521r1 (eq. 15360 bits RSA) FS 128
> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH secp521r1 (eq. 15360 bits RSA) FS 256
> # TLS 1.0 (server has no preference)
> TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH secp521r1 (eq. 15360 bits RSA) FS 128
> TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH secp521r1 (eq. 15360 bits RSA) FS 256
On the HTTPAPI/FTPAPI list, I was told that HTTPAPI uses the operating
system's SSL support (which was how I thought it worked), and directed
to look through the system values to see what it supports. What I found was:
QSSLPCL *SEC Secure sockets layer protocols
> *OPSYS
(which I'm pretty sure means that all OS-supported protocols are
available; they can also be individually specified as any or all of
*TLSV1, *SSLV3, and *SSLV2)
QSSLCSL *SEC Secure sockets layer cipher specification list
> *RSA_AES_128_CBC_SHA
> *RSA_RC4_128_SHA
> *RSA_RC4_128_MD5
> *RSA_AES_256_CBC_SHA
> *RSA_3DES_EDE_CBC_SHA
> *RSA_DES_CBC_SHA
> *RSA_EXPORT_RC4_40_MD5
> *RSA_EXPORT_RC2_CBC_40_MD5
> *RSA_NULL_SHA
> *RSA_NULL_MD5
and unfortunately, IBM doesn't backport new cipher suites to older OS
releases.
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Problem: (GSKit) No compatible cipher suite available between SSL
end points.
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
James,
On 10/3/17 5:52 PM, James H. H. Lampert wrote:
> Dear Mr. Klement, and members of the Tomcat List:
>
> I have a series of AS/400 programs using HTTPAPI to access
> services hosted by a webapp running under Tomcat.
>
> Up until now, I've only tested this configuration with Tomcat 7,
> running on a local Linux (CentOS) box, and the last time I tested
> it, it worked fine.
>
> Today, for the first time, I tried changing the HTTPAPI calls to
> access essentially the same webapp, only running in Tomcat 8 on a
> cloud server, in order to find any places where the calls need to
> be updated to keep up with changes in the services.
>
> And I didn't even get that far. Instead, the SSL handshake failed
> with
>> (GSKit) No compatible cipher suite available between SSL end
>> points.
>
> Now what?
>
> I mean, I know that I need to get HTTPAPI and Tomcat speaking the
> same language, but where do I begin?
First, I would check to see what Tomcat is actually advertising. There
are several ways to do that. One of them is to use Qualys's SSLLabs
server test:
https://www.ssllabs.com/ssltest/
Note that this tool only works for publicly-accessible servers.
If you have a private server, you'll need to resort to something a
little more complicated. I wrote a Java program to do just this. You
are welcome to use it:
https://wiki.apache.org/tomcat/tools/SSLTest.java
and
https://wiki.apache.org/tomcat/tools/SSLUtils.java
Once you know what cipher suites are actually supported by the server,
you can have a look at the ones supported by the HTTPAPI client to
make sure you have some overlap.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlnUMAIdHGNocmlzQGNo
cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFi7Rw//ZUb3T3GPjJ6yHjOs
bv09fY33iei8NXJYleHbzHs1XNVDRL8MMEtzc64g2DX9K5ducUqZEOpb5tSj7XiK
2uOsp5qaMplwFAgeY6kaAptaajuiz+WFDZXDOTRvcFTgwCEN2shsQDsJUd3EaXHj
NpduLueXpAY8B1V8GOAKQx2ZJxWO+puLDd8h0Ao/ojRmcxksFonBL8/Be6ZYTC4b
n5swZc9Hj8gs50ZkIrCfvNhOE+t7DJ2OH8WFJFdaNfHB/bWv1A3FyZ9bI9sgG+Ym
/EFH1khaWzH9AoB2Zv2dFD/D2ZDw2P30FJW1TZytcAQ6AhZo5fmMWNnKLMuu42Gw
EHGssKqohCIhQ7Cy5s3knigIwHURoXPo9shlDFJB/GQcTKcX8VCtTvDw23Ka0qQB
bjgmnrhb00dycBzFTiacG9RXrs7cMsYpgqzUFBTTYhDh0BhuQiwBQiTKo+dpoYab
XTuEPEeuUmV9HTW5+kPL1YXw8RSNxCgUvTA6w9jK4QE4CKp4WMi2ESAW/toB0XcR
yx9ZGqiDlYv732/8ID17P9/HN3GFskBGc90jjURmUtaLmPsidR9Ja7zU3zGHl2EQ
MyNTKrdpaXgwQMiFSNwbKqTXqY1Q6e4PfYjzsyPidah/FlhQd+nPXgievNLYp973
ifcIoyO9cd60yYnwW7y6TL3foXA=
=aRsw
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org