From owner-freebsd-hackers@freebsd.org Mon Sep 24 00:57:12 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B81B109F0E7 for ; Mon, 24 Sep 2018 00:57:12 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-3.mit.edu (dmz-mailsec-scanner-3.mit.edu [18.9.25.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9AD5F8A0BB; Mon, 24 Sep 2018 00:57:11 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190e-217ff7000000432a-af-5ba83533d83e Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id 0A.20.17194.33538AB5; Sun, 23 Sep 2018 20:52:04 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id w8O0pxgb031072; Sun, 23 Sep 2018 20:52:00 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w8O0ptGC020536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 23 Sep 2018 20:51:58 -0400 Date: Sun, 23 Sep 2018 19:51:55 -0500 From: Benjamin Kaduk To: Lev Serebryakov Cc: FreeBSD Hackers , Hans-Joerg Hoexer Subject: Re: Is there support for Intel Trusted Execution Engine? Message-ID: <20180924005155.GF24695@kduck.kaduk.org> References: <971906820.20180924011910@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <971906820.20180924011910@serebryakov.spb.ru> User-Agent: Mutt/1.9.1 (2017-09-22) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHIsWRmVeSWpSXmKPExsUixG6nomtiuiLaYNl3KYvtm/8xWszd9pHN onfVRlYHZo8Zn+azeMx6uY05gCmKyyYlNSezLLVI3y6BK+Pm6d+MBXNZKx78fsrSwNjO0sXI ySEhYCKx/eMPRhBbSGAxk0TvjoQuRi4geyOjxNZTLxghnKtMEoevzmMHqWIRUJXof9IG1s0m oCLR0H2ZGcQWAYq/+/8erIZZIEvi87sGVhBbWMBRYvuBI2AbeIG23Tv/EqiGA2iopUTrHTWI sKDEyZlPWCBatSRu/HvJBFLCLCAtsfwfB0iYU8BKouHpC7ApogLKEnv7DrFPYBSYhaR7FpLu WQjdCxiZVzHKpuRW6eYmZuYUpybrFicn5uWlFuka6+VmluilppRuYgQFK6ck3w7GSQ3ehxgF OBiVeHhX3F4eLcSaWFZcmXuIUZKDSUmUl/8fUIgvKT+lMiOxOCO+qDQntfgQowQHs5IIr9st oBxvSmJlVWpRPkxKmoNFSZx3QsviaCGB9MSS1OzU1ILUIpisDAeHkgTvT+MV0UKCRanpqRVp mTklCGkmDk6Q4TxAwz+B1PAWFyTmFmemQ+RPMSpKifNWmAAlBEASGaV5cL2gZCKRvb/mFaM4 0CvCvAkgVTzARATX/QpoMBPQ4CuzloAMLklESEk1MF5onLthmnR4Th3DBW21M6ln31z4s8Ko ue1vqGq74bP5l+/d2vVtiqqm39czV28qOpbrW+U97FS2lPz587DYjDvndq2qnRyt7syvHLyu ej1z97lnCf+m6cnVKH0KmPRyW9pHj2lfPka8P8B/hSdvr+RLpr3LI8xeKYXnZDwx2sci/Vjn MIdfja0SS3FGoqEWc1FxIgB55qCvAQMAAA== X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2018 00:57:12 -0000 On Mon, Sep 24, 2018 at 01:19:10AM +0300, Lev Serebryakov wrote: > Hello FreeBSD, > > I have system which contains, among other: > > none0@pci0:0:26:0: class=0x108000 card=0x72708086 chip=0x22988086 rev=0x35 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine' > class = encrypt/decrypt > > Looks like, tpm(8) doesn't support it. Is it worth supporting at all? Is it > TPM or something else? This is the Intel SGX technology, if I understand correctly. Which is not really the same sort of thing that tpm(8) seems to be doing. -Ben