Lines Matching full:com
7 https://www.openssh.com/txt/draft-ietf-secsh-filexfer-02.txt
17 1.1. transport: Protocol 2 MAC algorithm "umac-64@openssh.com"
23 https://www.openssh.com/txt/draft-miller-secsh-umac-01.txt
25 1.2. transport: Protocol 2 compression algorithm "zlib@openssh.com"
34 https://www.openssh.com/txt/draft-miller-secsh-compression-delayed-00.txt
36 1.3. transport: New public key algorithms "ssh-rsa-cert-v01@openssh.com",
37 "ssh-dsa-cert-v01@openssh.com",
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"
89 "aes128-gcm@openssh.com" or "aes256-gcm@openssh.com" and never as
94 1.7 transport: chacha20-poly1305@openssh.com authenticated encryption
132 string "ping@openssh.com"
146 "kex-strict-c-v00@openssh.com" to its kex_algorithms and the server
147 may append "kex-strict-s-v00@openssh.com". These pseudo-algorithms
177 "ext-info-in-auth@openssh.com" key via its initial SSH2_MSG_EXT_INFO
188 2.1. connection: Channel write close extension "eow@openssh.com"
203 signalling: "eow@openssh.com" (End Of Write). This message is sent by
209 string "eow@openssh.com"
217 remain open after a "eow@openssh.com" has been sent and more data may
228 "no-more-sessions@openssh.com"
233 request "no-more-sessions@openssh.com" to mitigate this attack.
240 string "no-more-sessions@openssh.com"
255 2.3. connection: Tunnel forward extension "tun@openssh.com"
257 OpenSSH supports layer 2 and layer 3 tunnelling via the "tun@openssh.com"
264 string "tun@openssh.com"
326 string "direct-streamlocal@openssh.com"
339 string "forwarded-streamlocal@openssh.com"
355 string "streamlocal-forward@openssh.com"
363 string "cancel-streamlocal-forward@openssh.com"
367 2.5. connection: hostkey update and rotation "hostkeys-00@openssh.com"
368 and "hostkeys-prove-00@openssh.com"
375 string "hostkeys-00@openssh.com"
386 it should send a "hostkeys-prove@openssh.com" message to request the
390 string "hostkeys-prove-00@openssh.com"
397 string "hostkeys-prove-00@openssh.com"
423 extension signal "INFO@openssh.com" that allows sending SIGINFO on
437 string "publickey-hostbound-v00@openssh.com"
452 string "publickey-hostbound@openssh.com"
494 4.3. sftp: Extension request "posix-rename@openssh.com"
502 string "posix-rename@openssh.com"
511 4.4. sftp: Extension requests "statvfs@openssh.com" and
512 "fstatvfs@openssh.com"
515 interfaces. The "statvfs@openssh.com" request operates on an explicit
519 string "statvfs@openssh.com"
522 The "fstatvfs@openssh.com" operates on an open file handle:
525 string "fstatvfs@openssh.com"
549 Both the "statvfs@openssh.com" and "fstatvfs@openssh.com" extensions are
552 4.5. sftp: Extension request "hardlink@openssh.com"
559 string "hardlink@openssh.com"
568 4.6. sftp: Extension request "fsync@openssh.com"
573 string "fsync@openssh.com"
582 4.7. sftp: Extension request "lsetstat@openssh.com"
589 string "lsetstat@openssh.com"
598 4.8. sftp: Extension request "limits@openssh.com"
605 string "limits@openssh.com"
641 4.9. sftp: Extension request "expand-path@openssh.com"
652 string "expand-path@openssh.com"
711 This provides similar information as the "expand-path@openssh.com" extension.
717 4.12. sftp: Extension request "users-groups-by-id@openssh.com"
726 string "users-groups-by-id@openssh.com"