From: "Dr. Greg Wettstein" <greg@wind.enjellic.com>
To: Christian Stroetmann <stroetmann@ontolab.com>
Cc: Pavel Machek <pavel@ucw.cz>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@suse.de>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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 02:02:08 -0600 [thread overview]
Message-ID: <201801040802.w04828Uj024983@wind.enjellic.com> (raw)
In-Reply-To: Christian Stroetmann <stroetmann@ontolab.com> "Re: [PATCH v6 00/11] Intel SGX Driver" (Jan 3, 3:00am)
On Jan 3, 3:00am, Christian Stroetmann wrote:
} Subject: Re: [PATCH v6 00/11] Intel SGX Driver
Good morning, I hope the day is going well for you.
> > Philosophically we take the approach that for high security
> > assurance environments that it is virtually impossible to allow
> > any untrusted code to run on a platform. Which is why we focus on
> > autonomous introspection for these environments.
> Interesting. I would like to hear more about this autonomous
> introspection concept, specifically what it monitors and how it
> reacts on an issue.
AI as we call it.. :-), at a high level, is the notion that an
operating system platform can be modeled for its intended behavior,
just as is done for buildings, bridges and airplanes. The model is
based on a precise mathematical description of the set of desired
information exchange events that the operating system will be allowed
to mediate.
Autonomous introspection is the notion of the platform using this
model to monitor and self-regulate its behavior.
> Maybe you have a summary or short introduction of the concept or/and
> a link to a document.
The initial concept and implementation were described by the following
Linux Security Summit paper:
http://kernsec.org/files/lss2015/idfusion-iso-identity-paper.pdf
The work has matured a great deal since then.
Most notably the modeling and control engine have been lifted out of
the kernel into an SGX enclave. In this architecture the kernel
cannot act without permission from the enclave based engine, which
requires the integrity of the enclave to be violated in order to
compromise the kernel.
A virtuous circle.
> Regards
> Christian Stroetmann
We can engage further in private e-mail as this may or may not be of
general interest.
Thanks for the interest.
Have a good day.
Greg
}-- End of excerpt from Christian Stroetmann
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
------------------------------------------------------------------------------
"Four year projections, are you kidding me. We don't know what we are
supposed to be doing at the 4 o'clock meeting this afternoon."
-- Terry Wieland
Resurrection
next reply other threads:[~2018-01-04 8:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 8:02 Dr. Greg Wettstein [this message]
2018-01-04 9:20 ` Christian Stroetmann
-- 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 21:09 Dr. Greg Wettstein
2018-01-04 9:06 Dr. Greg Wettstein
2018-01-09 14:25 ` Jarkko Sakkinen
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=201801040802.w04828Uj024983@wind.enjellic.com \
--to=greg@wind.enjellic.com \
--cc=Janakarajan.Natarajan@amd.com \
--cc=Kan.liang@intel.com \
--cc=bp@suse.de \
--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=pavel@ucw.cz \
--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=stroetmann@ontolab.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
Powered by JetHome