Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
MIME-Version: 1.0
In-Reply-To: <a806d9c3-7735-7fca-6b1e-db9cfd35c10d@apache.org>
References: <26897d05-0174-0dd1-e6f5-79b38aa9ebcc@apache.org>
 <BY2PR0501MB1717AA6A8C85CEA11A583CC9CC8A0@BY2PR0501MB1717.namprd05.prod.outlook.com>
 <a806d9c3-7735-7fca-6b1e-db9cfd35c10d@apache.org>
From: Konstantin Kolinko <knst.kolinko@gmail.com>
Date: Tue, 8 Aug 2017 16:22:37 +0300
Message-ID: <CABzHfVk-GXuJv9iG0OEJAroUaSjC2HhPN0Vo3cZRviAaZ89cXw@mail.gmail.com>
Subject: Re: Test keys and certs
To: Tomcat Developers List <dev@tomcat.apache.org>
Content-Type: text/plain; charset="UTF-8"
archived-at: Tue, 08 Aug 2017 13:22:46 -0000

2017-08-08 16:03 GMT+03:00 Mark Thomas <markt@apache.org>:
> On 08/08/17 13:59, George Stanchev wrote:
>
> <snip/>
>
>> 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-chrome-58/
>
> That did affect the server cert and we fixed that a little while ago. I
> don't believe it applies to user certs. The new user cert doesn't have a
> SAN and it is now working correctly in Chrome.

Interesting.

It means that for a simple self-signed cert the instructions [1] have
to be updated.

Looking at docs [2], there are examples of using '-ext' switch to set a SAN

keytool -alias ca -gencert -ext san=dns:ca1

Also -genkey switch was renamed to -genkeypair.


[1] tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html
[2] https://docs.oracle.com/javase/8/docs/technotes/tools/windows/keytool.html

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org