Hi Mark,
When I try to run Tomcat on the https server port:
*https://ip address:8444/*
It says as below:
--
*SSL connection error*
*ERR_SSL_PROTOCOL_ERROR*
*Unable to make a secure connection to the server. This may be a problem
with the server, or it may be requiring a client
Dear Tomcat team,thanks for your continuous support.
please assist us to find the root cause of the below problem.
during the start of tomcat server, the below error occurred.
Jul 30, 2015 6:57:38 AM org.apache.coyote.AbstractProtocol initINFO:
Initializing ProtocolHandler [http-bio-8585]Jul
Hi,
When can we expect the release of JK 1.2.41 source code?
Regards,
Chinoy
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Sunday, July 26, 2015 10:16 PM
To: Tomcat Users List users@tomcat.apache.org
Subject: Re: AW: Question concerning mod_jk Security Fix
On 05/08/2015 07:32, Nikitha Benny wrote:
Hi Mark,
When I try to run Tomcat on the https server port:
*https://ip address:8444/*
It says as below:
--
*SSL connection error*
*ERR_SSL_PROTOCOL_ERROR*
*Unable to make a secure connection to the server. This may be a problem
Hi Mark,
My server is not on a public domain.
How can i verify the setup which is on a private network?
Regards,
Nikitha
On Wed, Aug 5, 2015 at 2:14 PM, Mark Thomas ma...@apache.org wrote:
On 05/08/2015 07:32, Nikitha Benny wrote:
Hi Mark,
When I try to run Tomcat on the https server
Hi Nikhita,
run the sslscan tool from the command line or openssl s_client in debug mode
https://github.com/rbsec/sslscan
Regards,
Sanaullah
On Wed, Aug 5, 2015 at 2:23 PM, Nikitha Benny nikki.be...@gmail.com wrote:
Hi Mark,
My server is not on a public domain.
How can i verify the setup
Hi Mark, Sanaullah,
Thank you for your valuable suggestion.
I just ran the openssl s_client scan, and it looks like the server side is
running fine on *TLSv1.2* Protocol.
[root]## *openssl s_client -connect 16.183.93.84:8444
http://16.183.93.84:8444*
CONNECTED(0003)
- - - - - - -
- - - -
run this command with debugging prints.
openssl s_client -connect 16.183.93.84:8444 -debug -msg
Protocol : *TLSv1.2*
Cipher:
it seems something broken as there is no Cipher
Regards,
Sanaullah
On Wed, Aug 5, 2015 at 3:52 PM, Nikitha Benny nikki.be...@gmail.com wrote:
Hi Mark,
Hi Sanaullah,
That is because we have removed the entire ciphers attribute from the
server.xml file.
But that should be fine as the non complaint FIPS also has the cipher
attribute removed and it shows the similar client to server conection and
runs fine.
Regards,
Nikitha
On Wed, Aug 5, 2015 at
if you remove the entire ciphers attribute from the server.xml then by
default ssl/TLS session pick the best available cipher from the ssl/tls
handshake version.
On Wed, Aug 5, 2015 at 4:10 PM, Nikitha Benny nikki.be...@gmail.com wrote:
Hi Sanaullah,
That is because we have removed the
Am 5. August 2015 10:32:34 MESZ, schrieb Rahul Singh rksing...@hotmail.com:
Dear Tomcat team,thanks for your continuous support.
please assist us to find the root cause of the below problem.
during the start of tomcat server, the below error occurred.
Jul 30, 2015 6:57:38 AM
I'm trying to configure an e-mail session in my Tomcat configuration like this:
Resource name=mail/session
auth=Container
type=javax.mail.Session
mail.transport.protocol=smtp
mail.smtp.host=192.168.0.2
mail.debug=true /
From my web application, I'm instantiating a
12 matches
Mail list logo
