Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID check
"M. Ranganathan" <mranga@gmail.com> Fri, 03 April 2020 20:38 UTC
Return-Path: <mranga@gmail.com>
X-Original-To: iot-onboarding@ietfa.amsl.com
Delivered-To: iot-onboarding@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D17E03A0A11 for <iot-onboarding@ietfa.amsl.com>; Fri, 3 Apr 2020 13:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 uLExbgvic7h7 for <iot-onboarding@ietfa.amsl.com>; Fri, 3 Apr 2020 13:38:16 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 264473A0A0F for <iot-onboarding@ietf.org>; Fri, 3 Apr 2020 13:38:16 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id h131so9015037iof.1 for <iot-onboarding@ietf.org>; Fri, 03 Apr 2020 13:38:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=oDYtWr9lVDkJgjyqerVUmfCaK6LIMj24LIB7uu6iHOI=; b=oWd961Lg26DF/Cwv3JI9lV+6Q39cvc4f0AVMxD20C8Hn0BthXhct7mhbuIAGTBitF+ 2vYJEudtaEr2fEIA7ri+GJNXgQkzjqTgduTjMBVSmL2iJ5pCHCfG5/NUKvVWXdCWFRJY W231GMFACYCWxGMfzlXKvjCJYepl/y7nSEu2KLg04874hrDAhz/oLVVv2hdpZmTkUUjO zB/7hoSrfUiwVZuLKYBG0jY5OiKrpplIpb0Rm5Q4ekmBI7xHouglvYt5X9AKUfTjgNEM eeZAd8mDeoryi9nICFRTPa4psjtT0DySw9LdqZRGoxeCX46WEG60gLNOIW2kB6y1Gq5K nGDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=oDYtWr9lVDkJgjyqerVUmfCaK6LIMj24LIB7uu6iHOI=; b=Wqv5ObGCyyjEGmzzvP6ao9sPoa9IYodRWBLWuYllDO9GrkemnsQd0HzjLIjd9XtRIy FSIrLI55DPNju6pbujGWjUhkt8XelRKoc1JfXIaV88ueu1Cmvk+9skmpzYTvZOXUJv3J B+p8TW64WFUbTm639mNgJerTK20gt1HwR8RVmwh1PRnL5/T9iKpTOpLRY2yrVQ5UM7yb PBQjtv4+/icjGSMYBya/IRVokOwNsToF2ZRD7lllR62KDv3mGQyHWEyLPmns8dt8Bk2I j8wm8LGTRHsaDw0gJ3grMMSmBLcU20enCnInP9S74F/uaJTTNhoP55/vWAu8gAWQRp5k L1iw==
X-Gm-Message-State: AGi0PuaZF36PVL1JWO+/4dtbVa3uXAd7V1u2xSNRbTnEXfe4tgXlmneG 8/QQ58HJGVjZz5o98Mqix4GASMK5dBsmBDo+cL5qvvZc
X-Google-Smtp-Source: APiQypKd2I7FyPCj8mU4CT1u4PlR2KVsLKK2/e/XqEe4tyWW7BZVIif0Wc2pT5O6JimNULmD/sHmH6fGNMFkyX34hto=
X-Received: by 2002:a5d:9e4d:: with SMTP id i13mr9205079ioi.43.1585946294850; Fri, 03 Apr 2020 13:38:14 -0700 (PDT)
MIME-Version: 1.0
References: <CAHiu4JMF22GQBV+yNtN5ySUvJtcc8_+xj9biJLE9Dcc1YvUp9w@mail.gmail.com>
In-Reply-To: <CAHiu4JMF22GQBV+yNtN5ySUvJtcc8_+xj9biJLE9Dcc1YvUp9w@mail.gmail.com>
From: "M. Ranganathan" <mranga@gmail.com>
Date: Fri, 03 Apr 2020 16:37:38 -0400
Message-ID: <CAHiu4JP8B5sQ7y5CUtvX=3nENJx-pcFDkgeYDWFDwp2V5zC7Cw@mail.gmail.com>
To: iot-onboarding@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/Em9ypvGoUt_BAybJ3iS6WsHtYFQ>
Subject: Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID check
X-BeenThere: iot-onboarding@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IoT onboarding mechanisms <iot-onboarding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-onboarding/>
List-Post: <mailto:iot-onboarding@ietf.org>
List-Help: <mailto:iot-onboarding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-onboarding>, <mailto:iot-onboarding-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2020 20:38:18 -0000
Sorry to reply to my own post .... On Fri, Apr 3, 2020 at 12:45 PM M. Ranganathan <mranga@gmail.com> wrote: > > Hello, > > The EST spec says that if the password on a simpleenroll CSR exists > then that password should match the tls unique identifier of the HTTPS > connection (section 3.5). > Also TLS unique ID is deprecated in TLS 1.3 I believe. So does the channel binding check won't work anyway (?) > Given that BRSKI establishes a persistent HTTPS connection, is this > check even required? > > I looked at draft-richardson-anima-registrar-considerations but I > could not find anything about this so I would appreciate some > clarification. > > Thanks, > > Ranga > > > > -- > M. Ranganathan -- M. Ranganathan
- [Iot-onboarding] BRSKI-EST and TLS Unique ID check M. Ranganathan
- Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID … M. Ranganathan
- Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID … Dan Harkins
- Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID … M. Ranganathan
- Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID … Dan Harkins
- Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID … Michael Richardson
- Re: [Iot-onboarding] BRSKI-EST and TLS Unique ID … Michael Richardson