RFC 4819:Secure Shell Public Key Subsystem
RFC-Ref

public key


Click on the red underlined text to get to the source

... authenticate once with password authentication and transfer the public key to the server. However, to date no two implementations use the same mechanism to configure a public key for ...
... transfer the public key to the server. However, to date no two implementations use the same mechanism to configure a public key for use. ...
... allows client software to take on the burden of this configuration. The Public Key Subsystem protocol is designed for extreme simplicity in implementation. It is not intended as a Public Key Infrastructure ...
... The Public Key Subsystem protocol is designed for extreme simplicity in implementation. It is not intended as a Public Key Infrastructure for X.509 Certificates (PKIX ...
... The Secure Shell Public Key Subsystem has been designed to run on top of the Secure Shell transport layer ...
... servers SHOULD provide a configuration option to disable the use of password authentication after the first public key is added. ...


... Public Key Subsystem Overview ...
... The Public Key Subsystem provides a server-independent mechanism for clients ...
... well as provide specific response data. The format of public key blobs are detailed in Section 6.6, "Public Key Algorithms" of the SSH Transport Protocol document [2 ...
... The format of public key blobs are detailed in Section 6.6, "Public Key Algorithms" of the SSH Transport Protocol document [2]. ...
... Opening the Public Key Subsystem ...
... The Public Key Subsystem is started by a client sending an SSH ...
... Opening a Session". To open the Public Key Subsystem, the client sends: ...
... SSH_MSG_CHANNEL_SUCCESS if the Public Key Subsystem was successfully started, or SSH_MSG_CHANNEL ...
... CHANNEL_FAILURE if the server failed to start or does not support the Public Key Subsystem. The server SHOULD respond with SSH ...
... SSH_MSG_CHANNEL_FAILURE if the user is not allowed access to the Public Key Subsystem (for example, because the user authenticated with a restricted public key ...
... Public Key Subsystem (for example, because the user authenticated with a restricted public key). It is RECOMMENDED that clients ...
... All Public Key Subsystem requests and responses are sent in the following form: ...


... Public Key Subsystem Operations ...
... The Public Key Subsystem currently defines four operations: add, remove, list, and listattributes. ...
... Adding a Public Key ...
... If the client wishes to add a public key, the client sends: ...
... string "add" string public key algorithm name string public key blob ...
... string public key algorithm name string public key blob boolean overwrite uint32 ...
... attribute-count times The server MUST attempt to store the public key for the user in the appropriate location so the public key can be used for subsequent ...
... The server MUST attempt to store the public key for the user in the appropriate location so the public key can be used for subsequent public key authentications. If the overwrite field is false and the ...
... appropriate location so the public key can be used for subsequent public key authentications. If the overwrite field is false and the specified key already exists, the server MUST return SSH ...
... The value of the comment attribute contains user-specified text about the public key. The server SHOULD make every effort to preserve this value and return it with the key during any subsequent list operation. The server MUST NOT attempt to interpret or act upon the ...
... Removing a Public Key ...
... If the client wishes to remove a public key, the client sends: ...
... string "remove" string public key algorithm name string public key blob ...
... string public key algorithm name string public key blob The server MUST attempt to remove ...
... The server MUST attempt to remove the public key for the user from the appropriate location, so that the public key cannot be used for ...
... remove the public key for the user from the appropriate location, so that the public key cannot be used for subsequent authentications. ...
... string "publickey" string public key algorithm name string public key blob ...
... string public key algorithm name string public key blob uint32 attribute-count ...


... Public Key Subsystem Request Names ...
... The following table lists the initial assignments of Public Key Subsystem Request names. Request Name ...
... Public Key Subsystem Response Names ...
... The following table lists the initial assignments of Public Key Subsystem Response names. ...
... Public Key Subsystem Attribute Names ...
... Attributes are used to define properties or restrictions for public keys. The following table lists the initial assignments of Public Key Subsystem Attribute names. ...
... Public Key Subsystem Status Codes ...
... The following table identifies the initial assignments of the Public Key Subsystem status code values. ...



Google
Web
RFC-Ref