From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.20; helo=mga02.intel.com; envelope-from=star.zeng@intel.com; receiver=edk2-devel@lists.01.org Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 8E2B32194D387 for ; Thu, 18 Oct 2018 06:44:30 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Oct 2018 06:44:29 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,396,1534834800"; d="scan'208";a="83638681" Received: from shzintpr01.sh.intel.com (HELO [10.7.209.51]) ([10.239.4.80]) by orsmga006.jf.intel.com with ESMTP; 18 Oct 2018 06:44:27 -0700 To: Laszlo Ersek , Prasad Pandit Cc: Vincent Zimmer , edk2-devel@lists.01.org, "Cetola, Stephano" , Steve McIntyre <93sam@debian.org>, Peter Jones , Jiewen Yao , Michael Kinney , Gary Lin , Chao Zhang , star.zeng@intel.com References: <1539657661-57656-1-git-send-email-star.zeng@intel.com> <75a8ff0b-dac9-dbb4-a792-1085a0b73699@redhat.com> <2d9e4a50-be84-e501-b4b6-651367769e91@intel.com> <8f86065a-1170-9ad4-15f2-15f38bd54781@redhat.com> <87e85429-db40-0684-6895-a625cd020780@intel.com> <744b39e8-5811-bda3-0b7b-1195da73e702@redhat.com> From: "Zeng, Star" Message-ID: <5e33b676-0812-498a-9c51-b2ea94f56139@intel.com> Date: Thu, 18 Oct 2018 21:43:56 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <744b39e8-5811-bda3-0b7b-1195da73e702@redhat.com> Subject: Re: CVE-2018-3613 [was: MdeModulePkg Variable: Fix Timestamp zeroing issue on APPEND_WRITE] X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Oct 2018 13:44:30 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Hi Laszlo, On 2018/10/18 21:09, Laszlo Ersek wrote: > On a tangent: > > On 10/18/18 04:45, Zeng, Star wrote: >> On 2018/10/18 2:27, Laszlo Ersek wrote: > >>>>> http://mid.mail-archive.com/e62f7104-e341-6c7f-1af5-2130f161f111@redhat.com > >>>> Sorry, I could not access it. >>> >>> I'm unsure if you mean that you didn't see that message when I posted >>> it, or else that you've now tried to follow the link, but it doesn't >>> work for you. Does the official edk2-devel archive work perhaps? Here's >>> a link within that, to the same message: >>> >>> https://lists.01.org/pipermail/edk2-devel/2018-August/028700.html >> >> The edk2-devel archive link works for me. But I did not review this >> thread and did not see the request. :( > > OK, understood. > >> FYI, I could not access the redhat archive link >> http://mid.mail-archive.com/e62f7104-e341-6c7f-1af5-2130f161f111@redhat.com, >> I just heard some other people also could not access it. > > That link isn't a "Red Hat" link. It is a link that points to > > mid.mail-archive.com > > The site "mid.mail-archive.com" is a search service from > mail-archive.com. The URL is composed as follows: > > mid.mail-archive.com + "/" + > > In the part, the user can place the message-id header of > the email that they are looking for. > > In the current case, the Message-Id of the email that I wanted to direct > you to was: > > e62f7104-e341-6c7f-1af5-2130f161f111@redhat.com > > It ends with "@redhat.com" only because the message-id was originally > generated by a RH SMTP server (because the message was sent by me). So, > the complete link is not a "Red Hat" link; it is a mail-archive.com link > that happens to end with "@redhat.com" -- because the message ID that I > put in the URL, for the search service, ends with "@redhat.com". I am not familiar with using mail-archive.com. I just did some check and found it is interesting that I could access https://www.mail-archive.com/edk2-devel@lists.01.org/msg43513.html, it is because it has "https"? Not sure. Thanks, Star > > .... Anyway, I understand now that mail-archive.com may not be accessible > from behind the Great Firewall. I'll try to keep in mind to provide both > edk2-devel archive links, and mail-archive.com links. (Normally I prefer > mail-archive.com because it shows the thread structure much better.) > > Thanks! > Laszlo >