From: "Laszlo Ersek" <lersek@redhat.com>
To: sean.brogan@microsoft.com
Cc: devel@edk2.groups.io,
Sivaraman Nainar <sivaramann@amiindia.co.in>,
Jeremiah Cox <jerecox@microsoft.com>
Subject: Re: [edk2-devel] reg: Host Name Validation with Wild Card Certificate
Date: Sun, 8 Mar 2020 09:54:55 +0100 [thread overview]
Message-ID: <1181cf99-0752-3114-1ea3-54dd462fd5be@redhat.com> (raw)
In-Reply-To: <10736.1583620850271595025@groups.io>
On 03/07/20 23:40, Sean via Groups.Io wrote:
> The name of this flag is terrible but if you read the 2.8 spec.
> https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_A_Feb14.pdf
> page 1436.
> Says:
> EFI_TLS_VERIFY_FLAG_NONE means no additional flags set for hostname validation. Wildcards are supported and they match only in the left-most label.
>
> In the HttpDxe driver we made a change to support wildcards as wildcards are pretty commonly used in web services.
> https://github.com/microsoft/mu_basecore/commit/931ff1a45ce13a6a8c3e296f89c6de21f23a17ed#diff-45ead71899abef9932d2697dbd1d8867
>
> There is a lot of noise on this thread but its the best i can find.
> https://bugzilla.tianocore.org/show_bug.cgi?id=960
>
> We might need to open a new bugzilla as i think 960 is resolved but is too strict for practical usage.
Yes, please open a new Bugzilla ticket for investigating
EFI_TLS_VERIFY_FLAG_NO_WILDCARDS vs. EFI_TLS_VERIFY_FLAG_NONE.
Thanks!
Laszlo
prev parent reply other threads:[~2020-03-08 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 6:07 reg: Host Name Validation with Wild Card Certificate Sivaraman Nainar
2020-03-07 22:40 ` [edk2-devel] " Sean
2020-03-08 8:54 ` Laszlo Ersek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1181cf99-0752-3114-1ea3-54dd462fd5be@redhat.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox