Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 1 | This documents OpenSSH's deviations and extensions to the published SSH |
| 2 | protocol. |
| 3 | |
| 4 | Note that OpenSSH's sftp and sftp-server implement revision 3 of the SSH |
| 5 | filexfer protocol described in: |
| 6 | |
Darren Tucker | 461f50e | 2016-10-21 06:55:58 +1100 | [diff] [blame] | 7 | https://www.openssh.com/txt/draft-ietf-secsh-filexfer-02.txt |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 8 | |
Darren Tucker | a2e1048 | 2010-01-09 22:25:14 +1100 | [diff] [blame] | 9 | Newer versions of the draft will not be supported, though some features |
| 10 | are individually implemented as extensions described below. |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 11 | |
Damien Miller | 1e18beb | 2008-06-30 00:07:00 +1000 | [diff] [blame] | 12 | The protocol used by OpenSSH's ssh-agent is described in the file |
| 13 | PROTOCOL.agent |
| 14 | |
Damien Miller | eb8b60e | 2010-08-31 22:41:14 +1000 | [diff] [blame] | 15 | 1. Transport protocol changes |
| 16 | |
| 17 | 1.1. transport: Protocol 2 MAC algorithm "umac-64@openssh.com" |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 18 | |
| 19 | This is a new transport-layer MAC method using the UMAC algorithm |
| 20 | (rfc4418). This method is identical to the "umac-64" method documented |
| 21 | in: |
| 22 | |
Darren Tucker | 461f50e | 2016-10-21 06:55:58 +1100 | [diff] [blame] | 23 | https://www.openssh.com/txt/draft-miller-secsh-umac-01.txt |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 24 | |
Damien Miller | eb8b60e | 2010-08-31 22:41:14 +1000 | [diff] [blame] | 25 | 1.2. transport: Protocol 2 compression algorithm "zlib@openssh.com" |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 26 | |
| 27 | This transport-layer compression method uses the zlib compression |
| 28 | algorithm (identical to the "zlib" method in rfc4253), but delays the |
| 29 | start of compression until after authentication has completed. This |
| 30 | avoids exposing compression code to attacks from unauthenticated users. |
| 31 | |
| 32 | The method is documented in: |
| 33 | |
Darren Tucker | 461f50e | 2016-10-21 06:55:58 +1100 | [diff] [blame] | 34 | https://www.openssh.com/txt/draft-miller-secsh-compression-delayed-00.txt |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 35 | |
djm@openbsd.org | 8ba0fd4 | 2017-05-26 01:40:07 +0000 | [diff] [blame] | 36 | 1.3. transport: New public key algorithms "ssh-rsa-cert-v01@openssh.com", |
| 37 | "ssh-dsa-cert-v01@openssh.com", |
Damien Miller | eb8b60e | 2010-08-31 22:41:14 +1000 | [diff] [blame] | 38 | "ecdsa-sha2-nistp256-cert-v01@openssh.com", |
| 39 | "ecdsa-sha2-nistp384-cert-v01@openssh.com" and |
| 40 | "ecdsa-sha2-nistp521-cert-v01@openssh.com" |
Damien Miller | 0a80ca1 | 2010-02-27 07:55:05 +1100 | [diff] [blame] | 41 | |
Damien Miller | eb8b60e | 2010-08-31 22:41:14 +1000 | [diff] [blame] | 42 | OpenSSH introduces new public key algorithms to support certificate |
djm@openbsd.org | 523463a | 2015-02-16 22:13:32 +0000 | [diff] [blame] | 43 | authentication for users and host keys. These methods are documented |
| 44 | in the file PROTOCOL.certkeys |
Damien Miller | 0a80ca1 | 2010-02-27 07:55:05 +1100 | [diff] [blame] | 45 | |
Damien Miller | eb8b60e | 2010-08-31 22:41:14 +1000 | [diff] [blame] | 46 | 1.4. transport: Elliptic Curve cryptography |
| 47 | |
| 48 | OpenSSH supports ECC key exchange and public key authentication as |
| 49 | specified in RFC5656. Only the ecdsa-sha2-nistp256, ecdsa-sha2-nistp384 |
| 50 | and ecdsa-sha2-nistp521 curves over GF(p) are supported. Elliptic |
| 51 | curve points encoded using point compression are NOT accepted or |
| 52 | generated. |
| 53 | |
Damien Miller | af43a7a | 2012-12-12 10:46:31 +1100 | [diff] [blame] | 54 | 1.5 transport: Protocol 2 Encrypt-then-MAC MAC algorithms |
| 55 | |
| 56 | OpenSSH supports MAC algorithms, whose names contain "-etm", that |
| 57 | perform the calculations in a different order to that defined in RFC |
| 58 | 4253. These variants use the so-called "encrypt then MAC" ordering, |
| 59 | calculating the MAC over the packet ciphertext rather than the |
| 60 | plaintext. This ordering closes a security flaw in the SSH transport |
| 61 | protocol, where decryption of unauthenticated ciphertext provided a |
| 62 | "decryption oracle" that could, in conjunction with cipher flaws, reveal |
| 63 | session plaintext. |
| 64 | |
| 65 | Specifically, the "-etm" MAC algorithms modify the transport protocol |
| 66 | to calculate the MAC over the packet ciphertext and to send the packet |
| 67 | length unencrypted. This is necessary for the transport to obtain the |
| 68 | length of the packet and location of the MAC tag so that it may be |
| 69 | verified without decrypting unauthenticated data. |
| 70 | |
| 71 | As such, the MAC covers: |
| 72 | |
Damien Miller | 3739c8f | 2013-01-09 15:57:16 +1100 | [diff] [blame] | 73 | mac = MAC(key, sequence_number || packet_length || encrypted_packet) |
Damien Miller | af43a7a | 2012-12-12 10:46:31 +1100 | [diff] [blame] | 74 | |
Damien Miller | 3739c8f | 2013-01-09 15:57:16 +1100 | [diff] [blame] | 75 | where "packet_length" is encoded as a uint32 and "encrypted_packet" |
| 76 | contains: |
Damien Miller | af43a7a | 2012-12-12 10:46:31 +1100 | [diff] [blame] | 77 | |
| 78 | byte padding_length |
| 79 | byte[n1] payload; n1 = packet_length - padding_length - 1 |
| 80 | byte[n2] random padding; n2 = padding_length |
| 81 | |
Damien Miller | 1d75abf | 2013-01-09 16:12:19 +1100 | [diff] [blame] | 82 | 1.6 transport: AES-GCM |
| 83 | |
| 84 | OpenSSH supports the AES-GCM algorithm as specified in RFC 5647. |
| 85 | Because of problems with the specification of the key exchange |
| 86 | the behaviour of OpenSSH differs from the RFC as follows: |
| 87 | |
| 88 | AES-GCM is only negotiated as the cipher algorithms |
| 89 | "aes128-gcm@openssh.com" or "aes256-gcm@openssh.com" and never as |
| 90 | an MAC algorithm. Additionally, if AES-GCM is selected as the cipher |
| 91 | the exchanged MAC algorithms are ignored and there doesn't have to be |
| 92 | a matching MAC. |
| 93 | |
Damien Miller | 0fde8ac | 2013-11-21 14:12:23 +1100 | [diff] [blame] | 94 | 1.7 transport: chacha20-poly1305@openssh.com authenticated encryption |
| 95 | |
| 96 | OpenSSH supports authenticated encryption using ChaCha20 and Poly1305 |
| 97 | as described in PROTOCOL.chacha20poly1305. |
| 98 | |
Damien Miller | e4870c0 | 2013-12-05 10:22:39 +1100 | [diff] [blame] | 99 | 1.8 transport: curve25519-sha256@libssh.org key exchange algorithm |
| 100 | |
| 101 | OpenSSH supports the use of ECDH in Curve25519 for key exchange as |
| 102 | described at: |
| 103 | http://git.libssh.org/users/aris/libssh.git/plain/doc/curve25519-sha256@libssh.org.txt?h=curve25519 |
| 104 | |
Damien Miller | eb8b60e | 2010-08-31 22:41:14 +1000 | [diff] [blame] | 105 | 2. Connection protocol changes |
| 106 | |
| 107 | 2.1. connection: Channel write close extension "eow@openssh.com" |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 108 | |
| 109 | The SSH connection protocol (rfc4254) provides the SSH_MSG_CHANNEL_EOF |
| 110 | message to allow an endpoint to signal its peer that it will send no |
| 111 | more data over a channel. Unfortunately, there is no symmetric way for |
| 112 | an endpoint to request that its peer should cease sending data to it |
| 113 | while still keeping the channel open for the endpoint to send data to |
| 114 | the peer. |
| 115 | |
| 116 | This is desirable, since it saves the transmission of data that would |
| 117 | otherwise need to be discarded and it allows an endpoint to signal local |
| 118 | processes of the condition, e.g. by closing the corresponding file |
| 119 | descriptor. |
| 120 | |
| 121 | OpenSSH implements a channel extension message to perform this |
Darren Tucker | 1f781b1 | 2008-07-02 22:33:16 +1000 | [diff] [blame] | 122 | signalling: "eow@openssh.com" (End Of Write). This message is sent by |
| 123 | an endpoint when the local output of a session channel is closed or |
| 124 | experiences a write error. The message is formatted as follows: |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 125 | |
| 126 | byte SSH_MSG_CHANNEL_REQUEST |
| 127 | uint32 recipient channel |
| 128 | string "eow@openssh.com" |
| 129 | boolean FALSE |
| 130 | |
| 131 | On receiving this message, the peer SHOULD cease sending data of |
| 132 | the channel and MAY signal the process from which the channel data |
| 133 | originates (e.g. by closing its read file descriptor). |
| 134 | |
| 135 | As with the symmetric SSH_MSG_CHANNEL_EOF message, the channel does |
| 136 | remain open after a "eow@openssh.com" has been sent and more data may |
| 137 | still be sent in the other direction. This message does not consume |
| 138 | window space and may be sent even if no window space is available. |
| 139 | |
Damien Miller | 6385e75 | 2009-02-14 18:00:52 +1100 | [diff] [blame] | 140 | NB. due to certain broken SSH implementations aborting upon receipt |
| 141 | of this message (in contravention of RFC4254 section 5.4), this |
| 142 | message is only sent to OpenSSH peers (identified by banner). |
| 143 | Other SSH implementations may be whitelisted to receive this message |
| 144 | upon request. |
| 145 | |
Damien Miller | eb8b60e | 2010-08-31 22:41:14 +1000 | [diff] [blame] | 146 | 2.2. connection: disallow additional sessions extension |
| 147 | "no-more-sessions@openssh.com" |
Darren Tucker | 8901fa9 | 2008-06-11 09:34:01 +1000 | [diff] [blame] | 148 | |
| 149 | Most SSH connections will only ever request a single session, but a |
| 150 | attacker may abuse a running ssh client to surreptitiously open |
| 151 | additional sessions under their control. OpenSSH provides a global |
| 152 | request "no-more-sessions@openssh.com" to mitigate this attack. |
| 153 | |
| 154 | When an OpenSSH client expects that it will never open another session |
| 155 | (i.e. it has been started with connection multiplexing disabled), it |
| 156 | will send the following global request: |
| 157 | |
| 158 | byte SSH_MSG_GLOBAL_REQUEST |
| 159 | string "no-more-sessions@openssh.com" |
| 160 | char want-reply |
| 161 | |
| 162 | On receipt of such a message, an OpenSSH server will refuse to open |
| 163 | future channels of type "session" and instead immediately abort the |
| 164 | connection. |
| 165 | |
| 166 | Note that this is not a general defence against compromised clients |
| 167 | (that is impossible), but it thwarts a simple attack. |
| 168 | |
Damien Miller | 6385e75 | 2009-02-14 18:00:52 +1100 | [diff] [blame] | 169 | NB. due to certain broken SSH implementations aborting upon receipt |
| 170 | of this message, the no-more-sessions request is only sent to OpenSSH |
| 171 | servers (identified by banner). Other SSH implementations may be |
| 172 | whitelisted to receive this message upon request. |
| 173 | |
Damien Miller | eb8b60e | 2010-08-31 22:41:14 +1000 | [diff] [blame] | 174 | 2.3. connection: Tunnel forward extension "tun@openssh.com" |
Darren Tucker | e5d9829 | 2008-06-13 04:53:27 +1000 | [diff] [blame] | 175 | |
Damien Miller | bd45afb | 2008-06-30 00:04:57 +1000 | [diff] [blame] | 176 | OpenSSH supports layer 2 and layer 3 tunnelling via the "tun@openssh.com" |
Darren Tucker | e5d9829 | 2008-06-13 04:53:27 +1000 | [diff] [blame] | 177 | channel type. This channel type supports forwarding of network packets |
djm@openbsd.org | 4e636cf | 2015-05-08 03:56:51 +0000 | [diff] [blame] | 178 | with datagram boundaries intact between endpoints equipped with |
Darren Tucker | e5d9829 | 2008-06-13 04:53:27 +1000 | [diff] [blame] | 179 | interfaces like the BSD tun(4) device. Tunnel forwarding channels are |
| 180 | requested by the client with the following packet: |
| 181 | |
| 182 | byte SSH_MSG_CHANNEL_OPEN |
| 183 | string "tun@openssh.com" |
| 184 | uint32 sender channel |
| 185 | uint32 initial window size |
| 186 | uint32 maximum packet size |
| 187 | uint32 tunnel mode |
| 188 | uint32 remote unit number |
| 189 | |
| 190 | The "tunnel mode" parameter specifies whether the tunnel should forward |
| 191 | layer 2 frames or layer 3 packets. It may take one of the following values: |
| 192 | |
| 193 | SSH_TUNMODE_POINTOPOINT 1 /* layer 3 packets */ |
| 194 | SSH_TUNMODE_ETHERNET 2 /* layer 2 frames */ |
| 195 | |
| 196 | The "tunnel unit number" specifies the remote interface number, or may |
Darren Tucker | f2705c8 | 2010-01-08 18:54:17 +1100 | [diff] [blame] | 197 | be 0x7fffffff to allow the server to automatically chose an interface. A |
| 198 | server that is not willing to open a client-specified unit should refuse |
| 199 | the request with a SSH_MSG_CHANNEL_OPEN_FAILURE error. On successful |
| 200 | open, the server should reply with SSH_MSG_CHANNEL_OPEN_SUCCESS. |
Darren Tucker | e5d9829 | 2008-06-13 04:53:27 +1000 | [diff] [blame] | 201 | |
| 202 | Once established the client and server may exchange packet or frames |
| 203 | over the tunnel channel by encapsulating them in SSH protocol strings |
| 204 | and sending them as channel data. This ensures that packet boundaries |
| 205 | are kept intact. Specifically, packets are transmitted using normal |
| 206 | SSH_MSG_CHANNEL_DATA packets: |
| 207 | |
| 208 | byte SSH_MSG_CHANNEL_DATA |
| 209 | uint32 recipient channel |
| 210 | string data |
| 211 | |
| 212 | The contents of the "data" field for layer 3 packets is: |
| 213 | |
| 214 | uint32 packet length |
| 215 | uint32 address family |
| 216 | byte[packet length - 4] packet data |
| 217 | |
| 218 | The "address family" field identifies the type of packet in the message. |
| 219 | It may be one of: |
| 220 | |
| 221 | SSH_TUN_AF_INET 2 /* IPv4 */ |
| 222 | SSH_TUN_AF_INET6 24 /* IPv6 */ |
| 223 | |
| 224 | The "packet data" field consists of the IPv4/IPv6 datagram itself |
| 225 | without any link layer header. |
| 226 | |
Darren Tucker | f2705c8 | 2010-01-08 18:54:17 +1100 | [diff] [blame] | 227 | The contents of the "data" field for layer 2 packets is: |
Darren Tucker | e5d9829 | 2008-06-13 04:53:27 +1000 | [diff] [blame] | 228 | |
| 229 | uint32 packet length |
| 230 | byte[packet length] frame |
| 231 | |
Damien Miller | bd45afb | 2008-06-30 00:04:57 +1000 | [diff] [blame] | 232 | The "frame" field contains an IEEE 802.3 Ethernet frame, including |
Darren Tucker | e5d9829 | 2008-06-13 04:53:27 +1000 | [diff] [blame] | 233 | header. |
| 234 | |
Damien Miller | 7acefbb | 2014-07-18 14:11:24 +1000 | [diff] [blame] | 235 | 2.4. connection: Unix domain socket forwarding |
| 236 | |
| 237 | OpenSSH supports local and remote Unix domain socket forwarding |
| 238 | using the "streamlocal" extension. Forwarding is initiated as per |
| 239 | TCP sockets but with a single path instead of a host and port. |
| 240 | |
| 241 | Similar to direct-tcpip, direct-streamlocal is sent by the client |
| 242 | to request that the server make a connection to a Unix domain socket. |
| 243 | |
| 244 | byte SSH_MSG_CHANNEL_OPEN |
| 245 | string "direct-streamlocal@openssh.com" |
| 246 | uint32 sender channel |
| 247 | uint32 initial window size |
| 248 | uint32 maximum packet size |
| 249 | string socket path |
djm@openbsd.org | 90ee563 | 2016-04-08 06:35:54 +0000 | [diff] [blame] | 250 | string reserved |
| 251 | uint32 reserved |
Damien Miller | 7acefbb | 2014-07-18 14:11:24 +1000 | [diff] [blame] | 252 | |
| 253 | Similar to forwarded-tcpip, forwarded-streamlocal is sent by the |
| 254 | server when the client has previously send the server a streamlocal-forward |
| 255 | GLOBAL_REQUEST. |
| 256 | |
| 257 | byte SSH_MSG_CHANNEL_OPEN |
| 258 | string "forwarded-streamlocal@openssh.com" |
| 259 | uint32 sender channel |
| 260 | uint32 initial window size |
| 261 | uint32 maximum packet size |
| 262 | string socket path |
| 263 | string reserved for future use |
| 264 | |
| 265 | The reserved field is not currently defined and is ignored on the |
| 266 | remote end. It is intended to be used in the future to pass |
| 267 | information about the socket file, such as ownership and mode. |
| 268 | The client currently sends the empty string for this field. |
| 269 | |
| 270 | Similar to tcpip-forward, streamlocal-forward is sent by the client |
| 271 | to request remote forwarding of a Unix domain socket. |
| 272 | |
| 273 | byte SSH2_MSG_GLOBAL_REQUEST |
| 274 | string "streamlocal-forward@openssh.com" |
| 275 | boolean TRUE |
| 276 | string socket path |
| 277 | |
| 278 | Similar to cancel-tcpip-forward, cancel-streamlocal-forward is sent |
| 279 | by the client cancel the forwarding of a Unix domain socket. |
| 280 | |
| 281 | byte SSH2_MSG_GLOBAL_REQUEST |
| 282 | string "cancel-streamlocal-forward@openssh.com" |
| 283 | boolean FALSE |
| 284 | string socket path |
| 285 | |
djm@openbsd.org | 44732de | 2015-02-20 22:17:21 +0000 | [diff] [blame] | 286 | 2.5. connection: hostkey update and rotation "hostkeys-00@openssh.com" |
| 287 | and "hostkeys-prove-00@openssh.com" |
djm@openbsd.org | 8d4f872 | 2015-01-26 03:04:45 +0000 | [diff] [blame] | 288 | |
| 289 | OpenSSH supports a protocol extension allowing a server to inform |
djm@openbsd.org | 523463a | 2015-02-16 22:13:32 +0000 | [diff] [blame] | 290 | a client of all its protocol v.2 host keys after user-authentication |
djm@openbsd.org | 8d4f872 | 2015-01-26 03:04:45 +0000 | [diff] [blame] | 291 | has completed. |
| 292 | |
| 293 | byte SSH_MSG_GLOBAL_REQUEST |
djm@openbsd.org | 44732de | 2015-02-20 22:17:21 +0000 | [diff] [blame] | 294 | string "hostkeys-00@openssh.com" |
djm@openbsd.org | 8d4f872 | 2015-01-26 03:04:45 +0000 | [diff] [blame] | 295 | string[] hostkeys |
| 296 | |
djm@openbsd.org | 523463a | 2015-02-16 22:13:32 +0000 | [diff] [blame] | 297 | Upon receiving this message, a client should check which of the |
djm@openbsd.org | fcdb9d7 | 2018-02-19 00:55:02 +0000 | [diff] [blame] | 298 | supplied host keys are present in known_hosts. |
| 299 | |
| 300 | Note that the server may send key types that the client does not |
| 301 | support. The client should disgregard such keys if they are received. |
| 302 | |
| 303 | If the client identifies any keys that are not present for the host, |
| 304 | it should send a "hostkeys-prove@openssh.com" message to request the |
| 305 | server prove ownership of the private half of the key. |
djm@openbsd.org | 8d4f872 | 2015-01-26 03:04:45 +0000 | [diff] [blame] | 306 | |
djm@openbsd.org | 523463a | 2015-02-16 22:13:32 +0000 | [diff] [blame] | 307 | byte SSH_MSG_GLOBAL_REQUEST |
djm@openbsd.org | 44732de | 2015-02-20 22:17:21 +0000 | [diff] [blame] | 308 | string "hostkeys-prove-00@openssh.com" |
djm@openbsd.org | 523463a | 2015-02-16 22:13:32 +0000 | [diff] [blame] | 309 | char 1 /* want-reply */ |
| 310 | string[] hostkeys |
| 311 | |
| 312 | When a server receives this message, it should generate a signature |
| 313 | using each requested key over the following: |
| 314 | |
djm@openbsd.org | 44732de | 2015-02-20 22:17:21 +0000 | [diff] [blame] | 315 | string "hostkeys-prove-00@openssh.com" |
djm@openbsd.org | 523463a | 2015-02-16 22:13:32 +0000 | [diff] [blame] | 316 | string session identifier |
djm@openbsd.org | 523463a | 2015-02-16 22:13:32 +0000 | [diff] [blame] | 317 | string hostkey |
| 318 | |
| 319 | These signatures should be included in the reply, in the order matching |
| 320 | the hostkeys in the request: |
| 321 | |
| 322 | byte SSH_MSG_REQUEST_SUCCESS |
| 323 | string[] signatures |
| 324 | |
| 325 | When the client receives this reply (and not a failure), it should |
| 326 | validate the signatures and may update its known_hosts file, adding keys |
| 327 | that it has not seen before and deleting keys for the server host that |
| 328 | are no longer offered. |
| 329 | |
| 330 | These extensions let a client learn key types that it had not previously |
| 331 | encountered, thereby allowing it to potentially upgrade from weaker |
| 332 | key algorithms to better ones. It also supports graceful key rotation: |
| 333 | a server may offer multiple keys of the same type for a period (to |
| 334 | give clients an opportunity to learn them using this extension) before |
| 335 | removing the deprecated key from those offered. |
djm@openbsd.org | 8d4f872 | 2015-01-26 03:04:45 +0000 | [diff] [blame] | 336 | |
djm@openbsd.org | a46ac4d | 2018-10-02 12:51:58 +0000 | [diff] [blame] | 337 | 2.6. connection: SIGINFO support for "signal" channel request |
| 338 | |
| 339 | The SSH channels protocol (RFC4254 section 6.9) supports sending a |
| 340 | signal to a session attached to a channel. OpenSSH supports one |
| 341 | extension signal "INFO@openssh.com" that allows sending SIGINFO on |
| 342 | BSD-derived systems. |
| 343 | |
Damien Miller | eb8b60e | 2010-08-31 22:41:14 +1000 | [diff] [blame] | 344 | 3. SFTP protocol changes |
| 345 | |
| 346 | 3.1. sftp: Reversal of arguments to SSH_FXP_SYMLINK |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 347 | |
| 348 | When OpenSSH's sftp-server was implemented, the order of the arguments |
Damien Miller | bd45afb | 2008-06-30 00:04:57 +1000 | [diff] [blame] | 349 | to the SSH_FXP_SYMLINK method was inadvertently reversed. Unfortunately, |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 350 | the reversal was not noticed until the server was widely deployed. Since |
| 351 | fixing this to follow the specification would cause incompatibility, the |
| 352 | current order was retained. For correct operation, clients should send |
| 353 | SSH_FXP_SYMLINK as follows: |
| 354 | |
| 355 | uint32 id |
| 356 | string targetpath |
| 357 | string linkpath |
| 358 | |
Damien Miller | eb8b60e | 2010-08-31 22:41:14 +1000 | [diff] [blame] | 359 | 3.2. sftp: Server extension announcement in SSH_FXP_VERSION |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 360 | |
| 361 | OpenSSH's sftp-server lists the extensions it supports using the |
| 362 | standard extension announcement mechanism in the SSH_FXP_VERSION server |
| 363 | hello packet: |
| 364 | |
| 365 | uint32 3 /* protocol version */ |
| 366 | string ext1-name |
| 367 | string ext1-version |
| 368 | string ext2-name |
| 369 | string ext2-version |
| 370 | ... |
| 371 | string extN-name |
| 372 | string extN-version |
| 373 | |
| 374 | Each extension reports its integer version number as an ASCII encoded |
| 375 | string, e.g. "1". The version will be incremented if the extension is |
| 376 | ever changed in an incompatible way. The server MAY advertise the same |
| 377 | extension with multiple versions (though this is unlikely). Clients MUST |
Damien Miller | bd45afb | 2008-06-30 00:04:57 +1000 | [diff] [blame] | 378 | check the version number before attempting to use the extension. |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 379 | |
Damien Miller | eb8b60e | 2010-08-31 22:41:14 +1000 | [diff] [blame] | 380 | 3.3. sftp: Extension request "posix-rename@openssh.com" |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 381 | |
| 382 | This operation provides a rename operation with POSIX semantics, which |
| 383 | are different to those provided by the standard SSH_FXP_RENAME in |
| 384 | draft-ietf-secsh-filexfer-02.txt. This request is implemented as a |
| 385 | SSH_FXP_EXTENDED request with the following format: |
| 386 | |
| 387 | uint32 id |
| 388 | string "posix-rename@openssh.com" |
| 389 | string oldpath |
| 390 | string newpath |
| 391 | |
| 392 | On receiving this request the server will perform the POSIX operation |
| 393 | rename(oldpath, newpath) and will respond with a SSH_FXP_STATUS message. |
| 394 | This extension is advertised in the SSH_FXP_VERSION hello with version |
| 395 | "1". |
| 396 | |
Damien Miller | eb8b60e | 2010-08-31 22:41:14 +1000 | [diff] [blame] | 397 | 3.4. sftp: Extension requests "statvfs@openssh.com" and |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 398 | "fstatvfs@openssh.com" |
| 399 | |
| 400 | These requests correspond to the statvfs and fstatvfs POSIX system |
| 401 | interfaces. The "statvfs@openssh.com" request operates on an explicit |
| 402 | pathname, and is formatted as follows: |
| 403 | |
| 404 | uint32 id |
| 405 | string "statvfs@openssh.com" |
| 406 | string path |
| 407 | |
Damien Miller | bd45afb | 2008-06-30 00:04:57 +1000 | [diff] [blame] | 408 | The "fstatvfs@openssh.com" operates on an open file handle: |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 409 | |
| 410 | uint32 id |
| 411 | string "fstatvfs@openssh.com" |
| 412 | string handle |
| 413 | |
| 414 | These requests return a SSH_FXP_STATUS reply on failure. On success they |
| 415 | return the following SSH_FXP_EXTENDED_REPLY reply: |
| 416 | |
| 417 | uint32 id |
Darren Tucker | cd2ada6 | 2008-06-09 23:49:09 +1000 | [diff] [blame] | 418 | uint64 f_bsize /* file system block size */ |
| 419 | uint64 f_frsize /* fundamental fs block size */ |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 420 | uint64 f_blocks /* number of blocks (unit f_frsize) */ |
| 421 | uint64 f_bfree /* free blocks in file system */ |
| 422 | uint64 f_bavail /* free blocks for non-root */ |
| 423 | uint64 f_files /* total file inodes */ |
| 424 | uint64 f_ffree /* free file inodes */ |
| 425 | uint64 f_favail /* free file inodes for to non-root */ |
Darren Tucker | 17ec5d4 | 2008-06-09 23:47:37 +1000 | [diff] [blame] | 426 | uint64 f_fsid /* file system id */ |
Darren Tucker | cd2ada6 | 2008-06-09 23:49:09 +1000 | [diff] [blame] | 427 | uint64 f_flag /* bit mask of f_flag values */ |
| 428 | uint64 f_namemax /* maximum filename length */ |
Damien Miller | 58a8114 | 2008-05-19 16:11:56 +1000 | [diff] [blame] | 429 | |
| 430 | The values of the f_flag bitmask are as follows: |
| 431 | |
| 432 | #define SSH_FXE_STATVFS_ST_RDONLY 0x1 /* read-only */ |
| 433 | #define SSH_FXE_STATVFS_ST_NOSUID 0x2 /* no setuid */ |
| 434 | |
Damien Miller | c9c96f2 | 2008-07-05 15:17:48 +1000 | [diff] [blame] | 435 | Both the "statvfs@openssh.com" and "fstatvfs@openssh.com" extensions are |
| 436 | advertised in the SSH_FXP_VERSION hello with version "2". |
Darren Tucker | 17ec5d4 | 2008-06-09 23:47:37 +1000 | [diff] [blame] | 437 | |
djm@openbsd.org | ef100a2 | 2018-08-10 00:27:15 +0000 | [diff] [blame] | 438 | 3.5. sftp: Extension request "hardlink@openssh.com" |
Darren Tucker | af1f909 | 2010-12-05 09:02:47 +1100 | [diff] [blame] | 439 | |
| 440 | This request is for creating a hard link to a regular file. This |
| 441 | request is implemented as a SSH_FXP_EXTENDED request with the |
| 442 | following format: |
| 443 | |
| 444 | uint32 id |
| 445 | string "hardlink@openssh.com" |
| 446 | string oldpath |
| 447 | string newpath |
| 448 | |
| 449 | On receiving this request the server will perform the operation |
| 450 | link(oldpath, newpath) and will respond with a SSH_FXP_STATUS message. |
| 451 | This extension is advertised in the SSH_FXP_VERSION hello with version |
| 452 | "1". |
| 453 | |
djm@openbsd.org | ef100a2 | 2018-08-10 00:27:15 +0000 | [diff] [blame] | 454 | 3.6. sftp: Extension request "fsync@openssh.com" |
Damien Miller | f29238e | 2013-10-17 11:48:52 +1100 | [diff] [blame] | 455 | |
| 456 | This request asks the server to call fsync(2) on an open file handle. |
| 457 | |
| 458 | uint32 id |
| 459 | string "fsync@openssh.com" |
| 460 | string handle |
| 461 | |
| 462 | One receiving this request, a server will call fsync(handle_fd) and will |
| 463 | respond with a SSH_FXP_STATUS message. |
| 464 | |
| 465 | This extension is advertised in the SSH_FXP_VERSION hello with version |
| 466 | "1". |
| 467 | |
djm@openbsd.org | 7c71296 | 2018-08-10 00:42:29 +0000 | [diff] [blame] | 468 | 4. Miscellaneous changes |
| 469 | |
| 470 | 4.1 Public key format |
| 471 | |
| 472 | OpenSSH public keys, as generated by ssh-keygen(1) and appearing in |
| 473 | authorized_keys files, are formatted as a single line of text consisting |
| 474 | of the public key algorithm name followed by a base64-encoded key blob. |
djm@openbsd.org | e1b26ce | 2018-08-10 00:44:01 +0000 | [diff] [blame] | 475 | The public key blob (before base64 encoding) is the same format used for |
| 476 | the encoding of public keys sent on the wire: as described in RFC4253 |
| 477 | section 6.6 for RSA and DSA keys, RFC5656 section 3.1 for ECDSA keys |
| 478 | and the "New public key formats" section of PROTOCOL.certkeys for the |
| 479 | OpenSSH certificate formats. |
djm@openbsd.org | 7c71296 | 2018-08-10 00:42:29 +0000 | [diff] [blame] | 480 | |
| 481 | 4.2 Private key format |
| 482 | |
| 483 | OpenSSH private keys, as generated by ssh-keygen(1) use the format |
| 484 | described in PROTOCOL.key by default. As a legacy option, PEM format |
| 485 | (RFC7468) private keys are also supported for RSA, DSA and ECDSA keys |
| 486 | and were the default format before OpenSSH 7.8. |
| 487 | |
| 488 | 4.3 KRL format |
| 489 | |
| 490 | OpenSSH supports a compact format for Key Revocation Lists (KRLs). This |
| 491 | format is described in the PROTOCOL.krl file. |
| 492 | |
| 493 | 4.4 Connection multiplexing |
| 494 | |
| 495 | OpenSSH's connection multiplexing uses messages as described in |
| 496 | PROTOCOL.mux over a Unix domain socket for communications between a |
| 497 | master instance and later clients. |
| 498 | |
djm@openbsd.org | a46ac4d | 2018-10-02 12:51:58 +0000 | [diff] [blame] | 499 | $OpenBSD: PROTOCOL,v 1.36 2018/10/02 12:51:58 djm Exp $ |