From: Laszlo Ersek <lersek@redhat.com>
To: "Zeng, Star" <star.zeng@intel.com>, Prasad Pandit <ppandit@redhat.com>
Cc: Vincent Zimmer <Vincent.Zimmer@intel.com>,
edk2-devel@lists.01.org, "Cetola,
Stephano" <stephano.cetola@intel.com>,
Steve McIntyre <93sam@debian.org>,
Peter Jones <pjones@redhat.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Michael Kinney <michael.d.kinney@intel.com>,
Gary Lin <glin@suse.com>, Chao Zhang <chao.b.zhang@intel.com>
Subject: Re: CVE-2018-3613 [was: MdeModulePkg Variable: Fix Timestamp zeroing issue on APPEND_WRITE]
Date: Thu, 18 Oct 2018 15:09:51 +0200 [thread overview]
Message-ID: <744b39e8-5811-bda3-0b7b-1195da73e702@redhat.com> (raw)
In-Reply-To: <87e85429-db40-0684-6895-a625cd020780@intel.com>
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 + "/" + <Message-Id>
In the <Message-Id> 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
next prev parent reply other threads:[~2018-10-18 13:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 2:41 [PATCH] MdeModulePkg Variable: Fix Timestamp zeroing issue on APPEND_WRITE Star Zeng
2018-10-16 7:03 ` Yao, Jiewen
2018-10-17 13:10 ` CVE-2018-3613 [was: MdeModulePkg Variable: Fix Timestamp zeroing issue on APPEND_WRITE] Laszlo Ersek
2018-10-17 14:58 ` Zeng, Star
2018-10-17 18:27 ` Laszlo Ersek
2018-10-18 2:45 ` Zeng, Star
2018-10-18 13:09 ` Laszlo Ersek [this message]
2018-10-18 13:43 ` Zeng, Star
2018-10-18 16:04 ` Laszlo Ersek
2018-10-18 21:45 ` Laszlo Ersek
2018-10-19 7:09 ` Zeng, Star
2018-10-19 12:35 ` Laszlo Ersek
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=744b39e8-5811-bda3-0b7b-1195da73e702@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