-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 2/6/19 12:21, James H. H. Lampert wrote:
> Thanks. I do have some follow up questions
>
> On 2/6/19, 1:04 AM, Mark Thomas wrote:
>> On the TLS Connector:
>>
>> sslEnabledProtocols="TLSv1.1,TLSv1.2"
>
> Ok. So the active connector we cur
On 06/02/2019 17:21, James H. H. Lampert wrote:
> Thanks. I do have some follow up questions
>
> On 2/6/19, 1:04 AM, Mark Thomas wrote:
>> On the TLS Connector:
>>
>> sslEnabledProtocols="TLSv1.1,TLSv1.2"
>
> Ok. So the active connector we currently have for this particular
> installation (which
Thanks. I do have some follow up questions
On 2/6/19, 1:04 AM, Mark Thomas wrote:
On the TLS Connector:
sslEnabledProtocols="TLSv1.1,TLSv1.2"
Ok. So the active connector we currently have for this particular
installation (which has multiple IP addresses, hence the "address"
clause) is:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark and James,
On 2/6/19 04:04, Mark Thomas wrote:
> On 05/02/2019 23:49, James H. H. Lampert wrote:
>> We've just received word from a customer that they had two
>> vulnerabilities flagged on a security scan of the box their
>> Tomcat server is r
On 05/02/2019 23:49, James H. H. Lampert wrote:
> We've just received word from a customer that they had two
> vulnerabilities flagged on a security scan of the box their Tomcat
> server is running on.
>
> 38628 - TLS 1.0 still supported.
> Ok, assuming that the box and the JVM can go up to a more
We've just received word from a customer that they had two
vulnerabilities flagged on a security scan of the box their Tomcat
server is running on.
38628 - TLS 1.0 still supported.
Ok, assuming that the box and the JVM can go up to a more current TLS
level, and a more current cipher, what do I
