On Thu, Mar 26, 2015 at 2:32 PM, Ognjen Blagojevic
ognjen.d.blagoje...@gmail.com wrote:
Egor,
On 26.3.2015 21:23, Mark Thomas wrote:
On 26/03/2015 17:30, Egor Philippov wrote:
Anyone familiar with the warning or know
whether it represents a real security problem?
That depends on your
Hi,
We're serving our web and API content using Tomcat 8.0.20 using an HTTPs
connector that looks something like:
*Connector port=443
protocol=org.apache.coyote.http11.Http11NioProtocol*
*maxThreads=200 SSLEnabled=true scheme=https
clientAuth=false sslProtocol=TLS*
*compression=on
On 3/26/2015 1:30 PM, Egor Philippov wrote:
Hi,
We're serving our web and API content using Tomcat 8.0.20 using an HTTPs
connector that looks something like:
*Connector port=443
protocol=org.apache.coyote.http11.Http11NioProtocol*
*maxThreads=200 SSLEnabled=true scheme=https
On 26/03/2015 17:30, Egor Philippov wrote:
Anyone familiar with the warning or know
whether it represents a real security problem?
That depends on your definition of 'real'. I'm not aware of any viable
attacks but general opinion is that now is the time to take action.
Check your server
On Thu, Mar 26, 2015 at 10:42 AM, David kerber dcker...@verizon.net wrote:
On 3/26/2015 1:30 PM, Egor Philippov wrote:
Hi,
We're serving our web and API content using Tomcat 8.0.20 using an HTTPs
connector that looks something like:
*Connector port=443
On 3/26/2015 2:10 PM, Egor Philippov wrote:
On Thu, Mar 26, 2015 at 10:42 AM, David kerber dcker...@verizon.net wrote:
On 3/26/2015 1:30 PM, Egor Philippov wrote:
Hi,
We're serving our web and API content using Tomcat 8.0.20 using an HTTPs
connector that looks something like:
*Connector
Egor,
On 26.3.2015 21:23, Mark Thomas wrote:
On 26/03/2015 17:30, Egor Philippov wrote:
Anyone familiar with the warning or know
whether it represents a real security problem?
That depends on your definition of 'real'. I'm not aware of any viable
attacks but general opinion is that now is