Lines Matching full:protocol
1 This describes the protocol used by OpenSSH's ssh-agent.
3 OpenSSH's agent supports managing keys for the standard SSH protocol
4 2 as well as the legacy SSH protocol 1. Support for these key types
6 protocol 2 keys cannot see or affect protocol 1 keys and vice-versa.
8 Protocol 1 and protocol 2 keys are separated because of the differing
9 cryptographic usage: protocol 1 private RSA keys are used to decrypt
11 whereas protocol 2 RSA private keys are used to sign challenges with
16 With a couple of exceptions, the protocol message names used in this
18 messages refer to protocol 1 keys only. SSH2_* messages refer to
19 protocol 2 keys. Furthermore, the names also indicate whether the
22 protocol message names to their integer values.
26 Because of support for legacy SSH protocol 1 keys, OpenSSH's agent
27 protocol makes use of some data types not defined in RFC 4251.
51 2. Protocol Messages
53 All protocol messages are prefixed with their length in bytes, encoded
81 SSH2_AGENTC_ADD_IDENTITY requests for protocol 1 and protocol 2 keys
133 2.2.2 Add protocol 1 key
135 A client may add a protocol 1 key to an agent with the following
160 2.2.3 Add protocol 2 key
162 The OpenSSH agent supports DSA, ECDSA and RSA keys for protocol 2. DSA
237 order to the protocol 1 add keys message. As with the corresponding
238 protocol 1 "add key" request, the private key is overspecified to avoid
267 "pin" on the specified reader. The type of key loaded (protocol 1
268 or protocol 2) will be specified by the smartcard itself, it is not
278 A client may request that an agent delete all protocol 1 keys using the
283 This message requests the deletion of all protocol 2 keys:
291 Note that, to delete all keys (both protocol 1 and 2), a client
297 2.4.1 Removing a protocol 1 key
299 Removal of a protocol 1 key may be requested with the following message:
313 2.4.2 Removing a protocol 2 key
315 Protocol 2 keys may be removed with the following request:
321 Algorithms" for any of the supported protocol 2 key types.
351 requests exist for protocol 1 and protocol 2 keys.
353 2.5.1 Requesting a list of protocol 1 keys
355 To request a list of protocol 1 keys that are held in the agent, a
372 2.5.2 Requesting a list of protocol 2 keys
375 protocol 2 keys that are stored in the agent:
390 Algorithms" for any of the supported protocol 2 key types.
397 are separate requests for the protocol 1 and protocol 2 private key
400 2.6.1 Protocol 1 private key challenge
402 The private key operation used in version 1 of the SSH protocol is
417 1 <= encrypted_challenge < 2^256. "session_id" is the SSH protocol 1
443 2.6.2 Protocol 2 private key signature request
446 a protocol 2 key:
454 Algorithms" for any of the supported protocol 2 key types. "flags" is
510 Locking and unlocking affects both protocol 1 and protocol 2 keys.
512 3. Protocol message numbers
514 3.1 Requests from client to agent for protocol 1 key operations
523 3.2 Requests from client to agent for protocol 2 key operations
545 3.5 Replies from agent to client for protocol 1 key operations
550 3.6 Replies from agent to client for protocol 2 key operations
560 $OpenBSD: PROTOCOL.agent,v 1.6 2010/08/31 11:54:45 djm Exp $
