IETF Logo Mail Archive

Re: [Emu] Question for draft-ietf-emu-tls-eap-types-03

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 29 June 2021 22:40 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1BA93A15A2 for <emu@ietfa.amsl.com>; Tue, 29 Jun 2021 15:40:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level:
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NO_DNS_FOR_FROM=0.001, T_SPF_HELO_TEMPERROR=0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 sJnjTJeDvEdh for <emu@ietfa.amsl.com>; Tue, 29 Jun 2021 15:40:37 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF0B03A15A0 for <emu@ietf.org>; Tue, 29 Jun 2021 15:40:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 2614B38A31; Tue, 29 Jun 2021 18:42:38 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1VyVUAUBY6G9; Tue, 29 Jun 2021 18:42:36 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4015D38A2E; Tue, 29 Jun 2021 18:42:36 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id BED6E1801; Tue, 29 Jun 2021 18:40:32 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alan DeKok <aland@deployingradius.com>, EMU WG <emu@ietf.org>
In-Reply-To: <4F79B7DB-7E55-4564-88AE-C6E2AF8FD293@deployingradius.com>
References: <DB6D339A-710C-4EC4-9F8E-4B8602632AE1@deployingradius.com> <CABXxEz8EBUz_y1FmQTE9C8cpF+3vqy-mPCx8CnyUMZ72pNifAA@mail.gmail.com> <SJ0PR00MB1038767373E0DE9E3D7BE0DA95039@SJ0PR00MB1038.namprd00.prod.outlook.com> <C7DBE2EB-82BF-4229-B0AF-4BA48B2D45BC@deployingradius.com> <7332.1624927848@localhost> <4F79B7DB-7E55-4564-88AE-C6E2AF8FD293@deployingradius.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.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-sha512"; protocol="application/pgp-signature"
Date: Tue, 29 Jun 2021 18:40:32 -0400
Message-ID: <26359.1625006432@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/mA8VFaXruKwFuiEMHH7FTJ8x-x0>
Subject: Re: [Emu] Question for draft-ietf-emu-tls-eap-types-03
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jun 2021 22:40:43 -0000

Alan DeKok <aland@deployingradius.com> wrote:
    > On Jun 28, 2021, at 8:50 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    >> To date, Enterprises with laptops and PCs have provisioned the IDevID into
    >> the TPM, themselves, at the same time the device is wiped and the golden
    >> image is installed.  So, the TPM identity is actually known to them by construction.

    > And... if I have my own phone?  Or if a university wishes to tie
    > devices to student accounts?  So that they can limit (somewhat) abuses?

    > For now, the answer is "too bad".  Or maybe "buy a $$$$ MDM solution".

I think that today, the answer is probably too bad because too complex.
But, I think that most phones can do "Enterprise" WPA, and so a certificate
can be loaded in to do EAP-TLS.

    > As someone who bought my own phone, I'm not going install some MDM
    > solution which lets my employer wipe my personal device.  I would much
    > prefer to be able to prove (a) it's my device, and (b) it has a unique
    > device identifier.  The simpler the method, the better.

If I were a student, I would also not allow a university (or employer) MDM
solution onto my phone, and I'm not actually sure that it directly helps; it
just makes loading that certificate easier.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

v2.23.0 | Report a Bug | By Email