From: "Laszlo Ersek" <lersek@redhat.com>
To: "Wu, Jiaxin" <jiaxin.wu@intel.com>,
Sivaraman Nainar <sivaramann@amiindia.co.in>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Fu, Siyuan" <siyuan.fu@intel.com>
Cc: "Ramesh R." <rameshr@ami.com>,
"Madhan B. Santharam" <madhans@ami.com>,
Arun Subramanian B <arunsubramanianb@ami.com>,
Arun Sura Soundara Pandian <arunsuras@amiindia.co.in>,
Bhuvaneshwari M R <bhuvaneshwarimr@amiindia.co.in>
Subject: Re: TianoCore Bug 960 (HTTPS_HostName_Validation) Security Fix
Date: Fri, 25 Oct 2019 10:15:50 +0200 [thread overview]
Message-ID: <87347d27-cb29-22df-a880-720274fa48e7@redhat.com> (raw)
In-Reply-To: <895558F6EA4E3B41AC93A00D163B727416F84759@SHSMSX107.ccr.corp.intel.com>
On 10/25/19 04:18, Wu, Jiaxin wrote:
> Hi Siva,
>
> Let's wait the new series patches from Laszlo. Please also help to verify the new coming patches if possible.
>
> Laszlo,
>
> Can you also CC the new patches to Siva for the more verification?
Yes, I'll make sure Siva is added with Cc: tags to the patches.
Thanks!
Laszlo
> From: Sivaraman Nainar <sivaramann@amiindia.co.in>
> Sent: Thursday, October 24, 2019 5:06 PM
> To: devel@edk2.groups.io; Wu, Jiaxin <jiaxin.wu@intel.com>; Fu, Siyuan <siyuan.fu@intel.com>
> Cc: Ramesh R. <rameshr@ami.com>; Madhan B. Santharam <madhans@ami.com>; Arun Subramanian B <arunsubramanianb@ami.com>; Arun Sura Soundara Pandian <arunsuras@amiindia.co.in>; Bhuvaneshwari M R <bhuvaneshwarimr@amiindia.co.in>
> Subject: reg: TianoCore Bug 960 (HTTPS_HostName_Validation) Security Fix
>
> Hello Jiaxin:
>
> Could you please update when the security fixes for Host Name Validation will be submitted in the Main tree?
>
> UEFI 2.8 specification updated with the Host Name validation support already.
>
> -Siva
>
prev parent reply other threads:[~2019-10-25 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B4DE137BDB63634BAC03BD9DE765F197029AE233A8@VENUS1.in.megatrends.com>
2019-10-25 2:18 ` TianoCore Bug 960 (HTTPS_HostName_Validation) Security Fix Wu, Jiaxin
2019-10-25 8:15 ` 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=87347d27-cb29-22df-a880-720274fa48e7@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