[Cfrg] SHE Key Update Protocol
Henry B Hotz <hbhotz@oxy.edu> Wed, 11 April 2018 14:12 UTC
Return-Path: <hbhotz@oxy.edu>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C76B71201FA for <cfrg@ietfa.amsl.com>; Wed, 11 Apr 2018 07:12:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.536
X-Spam-Level:
X-Spam-Status: No, score=-3.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_SOFTFAIL=0.665] 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 R6FMNy95S4KZ for <cfrg@ietfa.amsl.com>; Wed, 11 Apr 2018 07:12:20 -0700 (PDT)
Received: from mailout.easymail.ca (mailout.easymail.ca [64.68.200.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68707126DC2 for <cfrg@irtf.org>; Wed, 11 Apr 2018 07:12:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 95F9A418D4; Wed, 11 Apr 2018 14:12:19 +0000 (UTC)
Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo03-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id flmnCMwLmn2c; Wed, 11 Apr 2018 14:12:19 +0000 (UTC)
Received: from [10.235.103.134] (unknown [198.51.250.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 3012141896; Wed, 11 Apr 2018 14:12:17 +0000 (UTC)
From: Henry B Hotz <hbhotz@oxy.edu>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Wed, 11 Apr 2018 07:12:16 -0700
Message-Id: <453BAC3A-1FE0-4422-AD9A-6ABDC4CC1849@oxy.edu>
To: cfrg@irtf.org
X-Mailer: iPhone Mail (15D100)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/pjx5LPKFfV8W1Asvtq5Ou3gtuHA>
Subject: [Cfrg] SHE Key Update Protocol
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2018 14:12:22 -0000
It’s an automotive thing. Anyone know of any published formal analysis/modeling of it? I’m especially interested in the requirements it imposes to maintain its assurances. Personal email. hbhotz@oxy.edu
- [Cfrg] SHE Key Update Protocol Henry B Hotz
- Re: [Cfrg] SHE Key Update Protocol =JeffH
- Re: [Cfrg] SHE Key Update Protocol Henry B Hotz