From: "David Woodhouse" <dwmw2@infradead.org>
To: devel@edk2.groups.io, lersek@redhat.com,
Sivaraman Nainar <sivaramann@amiindia.co.in>
Cc: "jiaxin.wu@intel.com" <jiaxin.wu@intel.com>,
"siyuan.fu@intel.com" <siyuan.fu@intel.com>
Subject: Re: [edk2-devel] reg: Multiple Host Name Certificate
Date: Thu, 20 Jun 2019 16:20:41 +0100 [thread overview]
Message-ID: <98a4ab4be8becd19be0695b164d3f9b9b2d89e58.camel@infradead.org> (raw)
In-Reply-To: <4d6fad2a-f052-4444-3a68-7e79aeda2082@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
On Thu, 2019-06-20 at 16:27 +0200, Laszlo Ersek wrote:
> It is indeed the bug that you think it is ("From code inspection I'd
> have guessed that the code would tolerate *any* valid certificate, even
> for a host other than the one it actually attempted to connect to.")
:)
> I'm CC'ing you on the BZ now, so you can read it even before it gets
> opened up.
... and I've pointed out the problem in the implementation of
TlsSetVerifyHost(). :)
Thanks.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
prev parent reply other threads:[~2019-06-20 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 11:51 reg: Multiple Host Name Certificate Sivaraman Nainar
2019-06-20 10:47 ` [edk2-devel] " David Woodhouse
2019-06-20 11:27 ` Sivaraman Nainar
2019-06-20 12:35 ` David Woodhouse
2019-06-20 14:27 ` Laszlo Ersek
2019-06-20 15:20 ` David Woodhouse [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=98a4ab4be8becd19be0695b164d3f9b9b2d89e58.camel@infradead.org \
--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