From: "Luck, Tony" <tony.luck@intel.com>
To: Hermann Ruckerbauer <Hermann.Ruckerbauer@EyeKnowHow.de>,
Borislav Petkov <bp@alien8.de>
Cc: He Zhe <zhe.he@windriver.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: EDAC list as Trojan Horse distribution ??
Date: Tue, 16 Mar 2021 19:51:56 +0000 [thread overview]
Message-ID: <4347e4ad4d544e778631ddd15eb88d28@intel.com> (raw)
In-Reply-To: <3a2cbcf1-388c-4524-907d-0592438320fc@email.android.com>
>> Nothing new - just the next spammer attempt.
> But this was a new class of Spam. So far i got only mass mailing... This was personalized based on my previous e-Mail (did not include this part in my mail)
Somewhat new - combining trawling of public mailing lists for addresses with
a phishing attack trying to get you to open a (presumably) malicious payload.
I haven't personally seen that ... probably my company's e-mail filters blocked it.
-Tony
next prev parent reply other threads:[~2021-03-16 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 6:39 [PATCH] x86/mce: Add compat_ioctl assignment to make it compatible with 32-bit system zhe.he
2020-04-16 8:40 ` He Zhe
2020-04-27 18:19 ` Luck, Tony
2020-05-02 14:18 ` He Zhe
[not found] ` <59d52031-f4e8-e754-c8b6-ca1130bf0cf1@EyeKnowHow.de>
2021-03-16 17:55 ` EDAC list as Trojan Horse distribution ?? Hermann Ruckerbauer
2021-03-16 18:03 ` Borislav Petkov
[not found] ` <3a2cbcf1-388c-4524-907d-0592438320fc@email.android.com>
2021-03-16 19:51 ` Luck, Tony [this message]
2021-03-18 8:58 ` Enrico Weigelt, metux IT consult
2021-03-20 19:22 ` Trojan horses on various lists was " Pavel Machek
2020-05-04 8:24 ` [tip: ras/core] x86/mcelog: Add compat_ioctl for 32-bit mcelog support tip-bot2 for He Zhe
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-all 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=4347e4ad4d544e778631ddd15eb88d28@intel.com \
--to=tony.luck@intel.com \
--cc=Hermann.Ruckerbauer@EyeKnowHow.de \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zhe.he@windriver.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.