Lines Matching full:keys

3 OpenSSH's agent supports managing keys for the standard SSH protocol
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
18 messages refer to protocol 1 keys only. SSH2_* messages refer to
19 protocol 2 keys. Furthermore, the names also indicate whether the
26 Because of support for legacy SSH protocol 1 keys, OpenSSH's agent
78 2.2 Adding keys to the agent
80 Keys are added to the agent using the SSH_AGENTC_ADD_RSA_IDENTITY and
81 SSH2_AGENTC_ADD_IDENTITY requests for protocol 1 and protocol 2 keys
85 and SSH2_AGENTC_ADD_ID_CONSTRAINED - these add keys with optional
88 OpenSSH may be built with support for keys hosted on a smartcard
89 or other hardware security module. These keys may be added
106 validity period has expired, OpenSSH's agent will erase these keys from
162 The OpenSSH agent supports DSA, ECDSA and RSA keys for protocol 2. DSA
163 keys may be added using the following request
185 ECDSA keys may be added using the following request
209 ED25519 keys may be added using the following request
228 For both ssh-ed25519 and ssh-ed25519-cert-v01@openssh.com keys, the private
231 RSA keys may be added with this request:
259 order to the protocol 1 add keys message. As with the corresponding
269 2.2.4 Loading keys from a smartcard
272 so, it supports an operation to load keys from a smartcard. Technically,
273 only the public components of the keys are loaded into the agent so
288 This operation may load all SSH keys that are unlocked using the
293 The agent will reply with a SSH_AGENT_SUCCESS if one or more keys have
298 2.3 Removing multiple keys
300 A client may request that an agent delete all protocol 1 keys using the
305 This message requests the deletion of all protocol 2 keys:
309 On success, the agent will delete all keys of the requested type and
313 Note that, to delete all keys (both protocol 1 and 2), a client
317 2.4 Removing specific keys
337 Protocol 2 keys may be removed with the following request:
349 2.4.3 Removing keys loaded from a smartcard
352 keys using this message:
362 smartcard-hosted keys, it will delete all keys that are hosted on the
365 The agent will reply with a SSH_AGENT_SUCCESS if one or more keys have
370 2.5 Requesting a list of known keys
372 An agent may be requested to list which keys it holds. Different
373 requests exist for protocol 1 and protocol 2 keys.
375 2.5.1 Requesting a list of protocol 1 keys
377 To request a list of protocol 1 keys that are held in the agent, a
387 Followed by zero or more consecutive keys, encoded as:
394 2.5.2 Requesting a list of protocol 2 keys
397 protocol 2 keys that are stored in the agent:
406 Followed by zero or more consecutive keys, encoded as:
488 An exception to this is for "ssh-dss" keys where the "flags" word
520 of keys.
532 Locking and unlocking affects both protocol 1 and protocol 2 keys.