On Tue, 8 Mar 2022 13:00:50 GMT, Sean Mullan wrote:
>> Please review this change to fully support RFC 6125 in the TLS
>> implementation. This change forbids wildcard domains in TLS certificates
>> unless the wildcard is in the left-most component. Certificates of this
>> nature should be rare
On Tue, 8 Mar 2022 12:56:50 GMT, Sean Mullan wrote:
>> test/jdk/sun/security/util/HostnameChecker/Wildcard.java line 72:
>>
>>> 70: } catch (Exception e) {
>>> 71: if (expected) {
>>> 72: throw new Exception("unexpectedly failed match", e);
>>
>> consider to
On Tue, 8 Mar 2022 13:00:50 GMT, Sean Mullan wrote:
>> Please review this change to fully support RFC 6125 in the TLS
>> implementation. This change forbids wildcard domains in TLS certificates
>> unless the wildcard is in the left-most component. Certificates of this
>> nature should be rare
On Mon, 7 Mar 2022 21:26:56 GMT, Rajan Halade wrote:
>> Sean Mullan has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Merge Wildcard test into TestHostnameCheck.
>> Rename HostnameMatcher dir to HostnameChecker.
>
> test/jdk/sun/security
On Mon, 7 Mar 2022 21:33:47 GMT, Sean Mullan wrote:
>> test/jdk/sun/security/util/HostnameMatcher/TestHostnameChecker.java line 196:
>>
>>> 194: check(checker, "5.6.7.8", cert3, true);
>>> 195: check(checker, "foo.bar.com", cert4, true);
>>> 196: check(checker, "altfoo.ba
> Please review this change to fully support RFC 6125 in the TLS
> implementation. This change forbids wildcard domains in TLS certificates
> unless the wildcard is in the left-most component. Certificates of this
> nature should be rare and are not allowed per the CABForum baseline
> requireme
On Mon, 7 Mar 2022 21:26:34 GMT, Rajan Halade wrote:
>> Please review this change to fully support RFC 6125 in the TLS
>> implementation. This change forbids wildcard domains in TLS certificates
>> unless the wildcard is in the left-most component. Certificates of this
>> nature should be rare
On Fri, 4 Mar 2022 14:59:54 GMT, Sean Mullan wrote:
> Please review this change to fully support RFC 6125 in the TLS
> implementation. This change forbids wildcard domains in TLS certificates
> unless the wildcard is in the left-most component. Certificates of this
> nature should be rare and
On Fri, 4 Mar 2022 14:59:54 GMT, Sean Mullan wrote:
> Please review this change to fully support RFC 6125 in the TLS
> implementation. This change forbids wildcard domains in TLS certificates
> unless the wildcard is in the left-most component. Certificates of this
> nature should be rare and
On Fri, 4 Mar 2022 16:48:47 GMT, Sean Mullan wrote:
> > About the CSR, did you have a plan to update the "Endpoint Identification
> > Algorithms" in the [Java Security Standard Algorithm
> > Names](https://docs.oracle.com/en/java/javase/17/docs/specs/security/standard-names.html#endpoint-identi
On Fri, 4 Mar 2022 16:33:45 GMT, Xue-Lei Andrew Fan wrote:
> About the CSR, did you have a plan to update the "Endpoint Identification
> Algorithms" in the [Java Security Standard Algorithm
> Names](https://docs.oracle.com/en/java/javase/17/docs/specs/security/standard-names.html#endpoint-ident
On Fri, 4 Mar 2022 14:59:54 GMT, Sean Mullan wrote:
> Please review this change to fully support RFC 6125 in the TLS
> implementation. This change forbids wildcard domains in TLS certificates
> unless the wildcard is in the left-most component. Certificates of this
> nature should be rare and
Please review this change to fully support RFC 6125 in the TLS implementation.
This change forbids wildcard domains in TLS certificates unless the wildcard is
in the left-most component. Certificates of this nature should be rare and are
not allowed per the CABForum baseline requirements. Howeve
13 matches
Mail list logo
