Distributing OpenPGP Key Fingerprints with Signed Keylist Subscriptions
draft-mccain-keylist-05
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | R. Miles McCain , Micah Lee , Nat Welch | ||
Last updated | 2020-03-05 (Latest revision 2019-09-02) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
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 specifies a system by which an OpenPGP client may subscribe to an organization's public keylist to keep its keystore up-to-date with correct keys from the correct keyserver(s), even in cases where the keys correspond to multiple (potentially uncontrolled) domains. Ensuring that all members or followers of an organization have their colleagues' most recent PGP public keys is critical to maintaining operational security. Without the most recent keys' fingerprints and a source of trust for those keys (as this document specifies), users must manually update and sign each others' keys -- a system that is untenable in larger organizations. This document proposes a experimental format for the keylist file as well as requirements for clients who wish to implement this experimental keylist subscription functionality.
Authors
R. Miles McCain
Micah Lee
Nat Welch
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)