Skip to main content

Secure Shell Public Key Subsystem
RFC 4819

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'Secure Shell defines a user authentication mechanism that is based on public keys, but does not …
Received changes through RFC Editor sync (changed abstract to 'Secure Shell defines a user authentication mechanism that is based on public 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 configure public keys in an implementation-independent fashion, allowing client software to take on the burden of this configuration.

The Public Key Subsystem provides a server-independent mechanism for clients to add public keys, remove public keys, and list the current public keys known by the server. Rights to manage public keys are specific and limited to the authenticated user.

A public key may also be associated with various restrictions, including a mandatory command or subsystem. [STANDARDS-TRACK]')
2015-10-14
(System) Notify list changed from secsh-chairs@ietf.org,bwijnen@lucent.com to bwijnen@lucent.com
2007-04-02
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2007-04-02
Amy Vezza [Note]: 'RFC 4819' added by Amy Vezza
2007-03-12
(System) RFC published