[Teep] Fwd: Restricted operating Environment
Benjamin Kaduk <kaduk@mit.edu> Tue, 19 November 2019 02:46 UTC
Return-Path: <kaduk@mit.edu>
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 89156120BCD for <teep@ietfa.amsl.com>; Mon, 18 Nov 2019 18:46:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=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 Q09xNqGQrT-q for <teep@ietfa.amsl.com>; Mon, 18 Nov 2019 18:46:51 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87D09120BB6 for <teep@ietf.org>; Mon, 18 Nov 2019 18:46:51 -0800 (PST)
Received: from mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id xAJ2klYD029736 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 18 Nov 2019 21:46:49 -0500
Date: Mon, 18 Nov 2019 18:46:47 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: teep@ietf.org
Cc: Laurence Lundblade <lgl@island-resort.com>
Message-ID: <20191119024647.GY32847@mit.edu>
References: <EC895C5D-69F2-419A-A71A-04FFFE77DF45@island-resort.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <EC895C5D-69F2-419A-A71A-04FFFE77DF45@island-resort.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/V25ttwtGGiAwJisvRekF9-OVfqc>
Subject: [Teep] Fwd: Restricted operating Environment
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 02:47:02 -0000
Forwarding Laurence's link about FIDO's "restricted operating environment" concept. -Ben On Tue, Nov 19, 2019 at 10:44:37AM +0800, Laurence Lundblade wrote: > > Keep in mind that this is part of a formal certification program who’s mission is to actually evaluate the security in a precise and well-defined way, and has the legal, financial and policy basis. This is very different from a protocol definition. > > https://fidoalliance.org/specs/fido-security-requirements-v1.0-fd-20170524/fido-authenticator-allowed-restricted-operating-environments-list_20170524.pdf > > LL >
- [Teep] Fwd: Restricted operating Environment Benjamin Kaduk
- [Teep] FW: Restricted operating Environment Hannes Tschofenig