[Medup] Update (-01) on Key Synchronization Protocol (KeySync)
Bernie Hoeneisen <bernie@ietf.hoeneisen.ch> Thu, 31 October 2019 20:46 UTC
Return-Path: <bernie@ietf.hoeneisen.ch>
X-Original-To: medup@ietfa.amsl.com
Delivered-To: medup@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87798120826 for <medup@ietfa.amsl.com>; Thu, 31 Oct 2019 13:46:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 qaeyD4YAtcl9 for <medup@ietfa.amsl.com>; Thu, 31 Oct 2019 13:46:53 -0700 (PDT)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [62.2.86.178]) (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 51336120801 for <medup@ietf.org>; Thu, 31 Oct 2019 13:46:53 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtp (Exim 4.86_2) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1iQHLG-0001si-TL for medup@ietf.org; Thu, 31 Oct 2019 21:46:50 +0100
Date: Thu, 31 Oct 2019 21:46:50 +0100
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: IETF MEDUP ML <medup@ietf.org>
Message-ID: <alpine.DEB.2.20.1910312139470.25390@softronics.hoeneisen.ch>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/medup/I-ds6DUXXJv14OpbwOQPlryYFKw>
Subject: [Medup] Update (-01) on Key Synchronization Protocol (KeySync)
X-BeenThere: medup@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Missing Elements for Decentralized and Usable Privacy <medup.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/medup>, <mailto:medup-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/medup/>
List-Post: <mailto:medup@ietf.org>
List-Help: <mailto:medup-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/medup>, <mailto:medup-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2019 20:46:55 -0000
Dear MEDUP List Please be informed that we have just submitted an update of the I-D on Key Synchronization Protocol (KeySync). This document describes the pEp KeySync protocol, which is designed to perform secure peer-to-peer synchronization of private keys across devices belonging to the same user. https://tools.ietf.org/html/draft-hoeneisen-pep-keysync-01 Among other things, we have also improved the readability and explanations thoughout the document. Don't hesitate to ask questions and submit your feedback to this list. We will also be around in Singapore. All the best Bernie ---------- Forwarded message ---------- [...] A new version of I-D, draft-hoeneisen-pep-keysync-01.txt has been successfully submitted by Bernie Hoeneisen and posted to the IETF repository. Name: draft-hoeneisen-pep-keysync Revision: 01 Title: pretty Easy privacy (pEp): Key Synchronization Protocol (KeySync) Document date: 2019-10-31 Group: Individual Submission Pages: 55 URL: https://www.ietf.org/internet-drafts/draft-hoeneisen-pep-keysync-01.txt Status: https://datatracker.ietf.org/doc/draft-hoeneisen-pep-keysync/ Htmlized: https://tools.ietf.org/html/draft-hoeneisen-pep-keysync-01 Htmlized: https://datatracker.ietf.org/doc/html/draft-hoeneisen-pep-keysync Diff: https://www.ietf.org/rfcdiff?url2=draft-hoeneisen-pep-keysync-01 Abstract: This document describes the pEp KeySync protocol, which is designed to perform secure peer-to-peer synchronization of private keys across devices belonging to the same user. Modern users of messaging systems typically have multiple devices for communicating, and attempting to use encryption on all of these devices often leads to situations where messages cannot be decrypted on a given device due to missing private key data. Current approaches to resolve key synchronicity issues are cumbersome and potentially unsecure. The pEp KeySync protocol is designed to facilitate this personal key synchronization in a user-friendly manner.
- [Medup] Update (-01) on Key Synchronization Proto… Bernie Hoeneisen