Comment 2Chinmayi Chandrasekhar
2021-09-08 10:52:25 UTC
@kahara: In the 4.6 Release Notes, I see the following under deprecated features:
The behavior of falling back to the Common Name field on X.509 certificates as a host name when no Subject Alternative Names are present is deprecated. In a future release, this behavior will be removed, and certificates must properly set the Subject Alternative Names field.
In 4.7+ versions, it is completely removed from the Release Notes document. Do you want it to be included back under the removed features heading? What is the exact update needed in the Release Notes document for 4.6+?
Hello Chinmayi,
> What is the exact update needed in the Release Notes document for 4.6+?
From the discussion in BZ#1889204, it seems that registries with non-SANs certificates are "already can't use" rather than just "deprecated" at 4.6.
If this is a specification, we should state that it does not work, not "deprecated".
Would you please confirm it as Eng/QE and update the documentation?
(In reply to Chinmayi Chandrasekhar from comment #2)
> @kahara: In the 4.6 Release Notes, I see the following under
> deprecated features:
>
> The behavior of falling back to the Common Name field on X.509 certificates
> as a host name when no Subject Alternative Names are present is deprecated.
> In a future release, this behavior will be removed, and certificates must
> properly set the Subject Alternative Names field.
>
> In 4.7+ versions, it is completely removed from the Release Notes document.
> Do you want it to be included back under the removed features heading? What
> is the exact update needed in the Release Notes document for 4.6+?
Comment 4Chinmayi Chandrasekhar
2021-09-14 11:52:52 UTC