On 14 August 2017 21:03:34 BST, Christopher Schultz
wrote:
>Mark,
>
>On 8/8/17 9:03 AM, Mark Thomas wrote:
>> On 08/08/17 13:59, George Stanchev wrote:
>>
>>
>>
>>> Is it possible the recent changes [1] has affected it? Chrome no
>longer looks in CN, which is ignored but rather expects SAN to
Mark,
On 8/8/17 9:03 AM, Mark Thomas wrote:
> On 08/08/17 13:59, George Stanchev wrote:
>
>
>
>> Is it possible the recent changes [1] has affected it? Chrome no longer
>> looks in CN, which is ignored but rather expects SAN to be filled up.
>> Perhaps Tomcat's test certs lack SAN?
>>
>> [1]
2017-08-08 16:03 GMT+03:00 Mark Thomas :
> On 08/08/17 13:59, George Stanchev wrote:
>
>
>
>> Is it possible the recent changes [1] has affected it? Chrome no longer
>> looks in CN, which is ignored but rather expects SAN to be filled up.
>> Perhaps Tomcat's test certs lack SAN?
>>
>> [1] https:
On 08/08/17 13:59, George Stanchev wrote:
> Is it possible the recent changes [1] has affected it? Chrome no longer looks
> in CN, which is ignored but rather expects SAN to be filled up. Perhaps
> Tomcat's test certs lack SAN?
>
> [1] https://www.thesslstore.com/blog/security-changes-in-chro
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Tuesday, August 08, 2017 5:23 AM
To: Tomcat Developers List
Subject: Test keys and certs
All,
Just a heads up.
A few days ago I started to look at bug 59423. I saw all sorts of errors when I
tried to configure a
ratch that
populates more of the fields and this does work with Chrome.
Therefore, I plan to replace our current test CA with the new one I have
created and, therefore, also replace all the test keys and certs used in
the unit tests. I'll also update the notes for creating these files and
t
