From: "Dr. Greg Wettstein" <greg@wind.enjellic.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Cedric Blancher <cedric.blancher@gmail.com>
Cc: "Jarkko Sakkinen" <jarkko.sakkinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org, x86@kernel.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Borislav Petkov" <bp@suse.de>,
"David S. Miller" <davem@davemloft.net>,
"Grzegorz Andrejczuk" <grzegorz.andrejczuk@intel.com>,
"Haim Cohen" <haim.cohen@intel.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Janakarajan Natarajan" <Janakarajan.Natarajan@amd.com>,
"Jim Mattson" <jmattson@google.com>,
"Kan Liang" <Kan.liang@intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"Kyle Huey" <me@kylehuey.com>, "Len Brown" <len.brown@intel.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"open list:FILESYSTEMS (VFS and infrastructure)"
<linux-fsdevel@vger.kernel.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Piotr Luc" <piotr.luc@intel.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Sean Christopherson" <sean.j.christopherson@intel.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Tom Lendacky" <thomas.lendacky@amd.com>,
"Vikas Shivappa" <vikas.shivappa@linux.intel.com>
Subject: Re: [PATCH v6 00/11] Intel SGX Driver
Date: Thu, 4 Jan 2018 15:09:06 -0600 [thread overview]
Message-ID: <201801042109.w04L961C032047@wind.enjellic.com> (raw)
In-Reply-To: Greg Kroah-Hartman <gregkh@linuxfoundation.org> "Re: [PATCH v6 00/11] Intel SGX Driver" (Jan 4, 3:27pm)
On Jan 4, 3:27pm, Greg Kroah-Hartman wrote:
} Subject: Re: [PATCH v6 00/11] Intel SGX Driver
Wild day, enjoyed by all I'm sure.
> On Thu, Jan 04, 2018 at 03:17:24PM +0100, Cedric Blancher wrote:
> > So how does this protect against the MELTDOWN attack (CVE-2017-5754)
> > and the MELTATOMBOMBA4 worm which uses this exploit?
> It has nothing to do with it at all, sorry.
Precision seems to be everything in these discussions.
Since SGX obviously does not mitigate micro-architectural state
probing it is not an effective general remediation against MELTDOWN.
Does your statement indicate there is solid documentation that
MELTDOWN can be used by a process of any privilege level to dump out
the unencrypted contents of an initialized enclave?
That would obviously be a big story as well.
> greg k-h
Have a good evening.
Greg
}-- End of excerpt from Greg Kroah-Hartman
As always,
Dr. G.W. Wettstein, Ph.D. Enjellic Systems Development, LLC.
4206 N. 19th Ave. Specializing in information infra-structure
Fargo, ND 58102 development.
PH: 701-281-1686
FAX: 701-281-3949 EMAIL: greg@enjellic.com
------------------------------------------------------------------------------
"If you get to thinkin' you're a person of some influence, try
orderin' somebody else's dog around."
-- Cowboy Wisdom
next reply other threads:[~2018-01-04 21:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 21:09 Dr. Greg Wettstein [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-09 21:50 Dr. Greg Wettstein
2018-01-10 16:16 ` Jarkko Sakkinen
2018-01-05 9:50 Dr. Greg Wettstein
2018-01-04 9:06 Dr. Greg Wettstein
2018-01-09 14:25 ` Jarkko Sakkinen
2018-01-04 8:02 Dr. Greg Wettstein
2018-01-04 9:20 ` Christian Stroetmann
2018-01-03 0:59 Dr. Greg Wettstein
2018-01-03 2:00 ` Christian Stroetmann
2018-01-03 9:48 ` Pavel Machek
2017-12-27 10:30 Dr. Greg Wettstein
2017-12-27 20:46 ` Pavel Machek
2017-11-25 19:29 Jarkko Sakkinen
2017-12-12 14:07 ` Pavel Machek
2017-12-14 11:18 ` Jarkko Sakkinen
2017-12-19 23:33 ` Jarkko Sakkinen
2017-12-20 13:18 ` Jarkko Sakkinen
2018-01-04 14:17 ` Cedric Blancher
2018-01-04 14:27 ` Greg Kroah-Hartman
2018-01-04 19:18 ` Ozgur
2018-01-04 15:08 ` James Bottomley
2018-01-09 14:27 ` Jarkko Sakkinen
2018-02-08 8:46 ` Pavel Machek
2018-02-08 13:48 ` Jarkko Sakkinen
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=201801042109.w04L961C032047@wind.enjellic.com \
--to=greg@wind.enjellic.com \
--cc=Janakarajan.Natarajan@amd.com \
--cc=Kan.liang@intel.com \
--cc=bp@suse.de \
--cc=cedric.blancher@gmail.com \
--cc=davem@davemloft.net \
--cc=greg@enjellic.com \
--cc=gregkh@linuxfoundation.org \
--cc=grzegorz.andrejczuk@intel.com \
--cc=haim.cohen@intel.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmattson@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=me@kylehuey.com \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=piotr.luc@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=vikas.shivappa@linux.intel.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®