Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 9519

Authors:

J. Galbraith
J. Van Dyke
J. Bright

Stream:

IETF

Source:

secsh (sec)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC4819

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 4819

Abstract

Secure Shell defines a user authentication mechanism that is based onpublic keys, but does not define any mechanism for key distribution.No common key management solution exists in current implementations.This document describes a protocol that can be used to configurepublic keys in an implementation-independent fashion, allowing clientsoftware to take on the burden of this configuration.

The Public Key Subsystem provides a server-independent mechanism forclients to add public keys, remove public keys, and list the currentpublic keys known by the server. Rights to manage public keys arespecific and limited to the authenticated user.

A public key may also be associated with various restrictions,including a mandatory command or subsystem. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.