pretty Easy privacy (pEp): Key Synchronization Protocol (KeySync)
draft-pep-keysync-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Volker Birk , Bernie Hoeneisen , Kelly Bristol | ||
| Last updated | 2020-05-07 (Latest revision 2019-11-04) | ||
| Replaces | draft-hoeneisen-pep-keysync | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
Volker Birk
Bernie Hoeneisen
Kelly Bristol
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)