Am 03.05.2016 um 16:53 schrieb Mark Thomas:
Hi,
OpenSSL have released the details of the security fixed in 1.0.2h. I've
looked through them quickly and it looks like at least CVE-2016-2107 is
applicable to Tomcat-Native.
Given that I haven't got 9.0.x to the point where it is ready to release
a
2016-05-03 16:53 GMT+02:00 Mark Thomas :
> Hi,
>
> OpenSSL have released the details of the security fixed in 1.0.2h. I've
> looked through them quickly and it looks like at least CVE-2016-2107 is
> applicable to Tomcat-Native.
>
> Given that I haven't got 9.0.x to the point where it is ready to r
On 03/05/2016 16:27, Rémy Maucherat wrote:
> 2016-05-03 16:53 GMT+02:00 Mark Thomas :
>
>> Hi,
>>
>> OpenSSL have released the details of the security fixed in 1.0.2h. I've
>> looked through them quickly and it looks like at least CVE-2016-2107 is
>> applicable to Tomcat-Native.
>>
>> Given that I
2016-05-03 17:53 GMT+03:00 Mark Thomas :
> Hi,
>
> OpenSSL have released the details of the security fixed in 1.0.2h. I've
> looked through them quickly and it looks like at least CVE-2016-2107 is
> applicable to Tomcat-Native.
>
> Given that I haven't got 9.0.x to the point where it is ready to re
2016-05-03 16:53 GMT+02:00 Mark Thomas :
> Hi,
>
> OpenSSL have released the details of the security fixed in 1.0.2h. I've
> looked through them quickly and it looks like at least CVE-2016-2107 is
> applicable to Tomcat-Native.
>
> Given that I haven't got 9.0.x to the point where it is ready to r
Hi,
OpenSSL have released the details of the security fixed in 1.0.2h. I've
looked through them quickly and it looks like at least CVE-2016-2107 is
applicable to Tomcat-Native.
Given that I haven't got 9.0.x to the point where it is ready to release
and that it is likely to take a couple more day
