From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=209.132.183.28; helo=mx1.redhat.com; envelope-from=lersek@redhat.com; receiver=edk2-devel@lists.01.org Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (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 4973021142FFE for ; Thu, 18 Oct 2018 06:09:55 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id B9E2F3082A26; Thu, 18 Oct 2018 13:09:54 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-121-50.rdu2.redhat.com [10.10.121.50]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5B27F100164E; Thu, 18 Oct 2018 13:09:52 +0000 (UTC) To: "Zeng, Star" , 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 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> From: Laszlo Ersek Message-ID: <744b39e8-5811-bda3-0b7b-1195da73e702@redhat.com> Date: Thu, 18 Oct 2018 15:09:51 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <87e85429-db40-0684-6895-a625cd020780@intel.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.45]); Thu, 18 Oct 2018 13:09:54 +0000 (UTC) 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:09:55 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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". ... 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