IETF Logo Mail Archive

Re: [Teep] My BoF impression

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 04 April 2017 13:54 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: teep@ietfa.amsl.com
Delivered-To: teep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0469D12869B for <teep@ietfa.amsl.com>; Tue, 4 Apr 2017 06:54:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tQWrwcPnKRCQ for <teep@ietfa.amsl.com>; Tue, 4 Apr 2017 06:54:50 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05F901296BA for <teep@ietf.org>; Tue, 4 Apr 2017 06:54:48 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 43E292009E for <teep@ietf.org>; Tue, 4 Apr 2017 10:19:02 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id CEFBD636BB for <teep@ietf.org>; Tue, 4 Apr 2017 09:54:46 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: teep <teep@ietf.org>
In-Reply-To: <22755.33183.740819.743679@fireball.acr.fi>
References: <HE1PR0802MB2475515770704882F9CFBDBCFA080@HE1PR0802MB2475.eurprd08.prod.outlook.com> <22755.33183.740819.743679@fireball.acr.fi>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 04 Apr 2017 09:54:46 -0400
Message-ID: <12099.1491314086@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/nUxODtyH5d-U0hzam1CSkRz6hrg>
Subject: Re: [Teep] My BoF impression
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: A Protocol for Dynamic Trusted Execution Environment Enablement <teep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teep>, <mailto:teep-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teep/>
List-Post: <mailto:teep@ietf.org>
List-Help: <mailto:teep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teep>, <mailto:teep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Apr 2017 13:54:52 -0000

Tero Kivinen <kivinen@iki.fi> wrote:
    > 2) The Secure trusted appliation marketplace needs to be able
    > to verify that the TEE wanting to install an application is
    > actual TEE, and not some fake device, for example using
    > signature from the key installed by the manufacturer which is
    > used to sign the installation request.

    > 3) The Secure trusted application marketplace can then encrypt
    > the trusted application with TEE specific key, so that nobody
    > else than TEE can decrypt and install it. This will prevent
    > leaking out confidential material inside the application.
    > Trusted application instlal package might also be personalized
    > for the specific TEE. Secure trusted application marketplace
    > will also sign the trusted application install package, so TEE
    > can verify it is authentic.

And yet, this can mean that end-user and even app-writers can not verify what
code they are actually running.

I think we need to very carefully seperate signed (and auditable) code from
encrypted data.  And said encrypted data has to be non-executable, and the
auditable code has to be verified to not include a Turing machine.... no
(encrypted) data driven programming allowed.



--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email