Attachment 3238 Details for Bug 2949 – PROTOCOL v1

PROTOCOL v1

PROTOCOL.limits.v1.1 (text/plain), 1.47 KB, created by Mike Frysinger on 2019-02-08 08:56:23 AEDT

(hide)

Description:

Filename:

MIME Type:

Creator: Mike Frysinger

Created: 2019-02-08 08:56:23 AEDT

Size: 1.47 KB

patch

obsolete

>sftp: Extension request "limits@openssh.com"
>
>This request is used to determine various limits the server might impose.
>Clients should not attempt to exceed these limits as the server might sever
>the connection immediately.
>
>    uint32      id
>    string      "limits@openssh.com"
>
>The server will respond with a SSH_FXP_EXTENDED_REPLY reply:
>
>    uint32      id
>    uint64      max-packet-length
>    uint64      max-read-length
>    uint64      max-write-length
>    uint64      max-open-handles
>
>The 'max-packet-length' applies to the total number of bytes in a single SFTP
>packet.  Servers SHOULD set this at least to 34000.
>
>The 'max-read-length' is the largest length in a SSH_FXP_READ packet.  Even if
>the client requests a larger size, servers will usually respond with a shorter
>SSH_FXP_DATA packet.  Servers SHOULD set this at least to 32768.
>
>The 'max-write-length' is the largest length in a SSH_FXP_WRITE packet the
>server will accept.  Servers SHOULD set this at least to 32768.
>
>The 'max-open-handles' is the maximum number of active handles that the server
>allows (e.g. handles created by SSH_FXP_OPEN and SSH_FXP_OPENDIR packets).
>
>If the server doesn't enforce a specific limit, then the field may be set to 0.
>This implies the server relies on the OS to enforce limits (e.g. available
>memory or file handles), and such limits might be dynamic.  The client SHOULD
>take care to not try to exceed reasonable limits.
>
>This extension is advertised in the SSH_FXP_VERSION hello with version
>"1".

Actions: View

Attachments on bug 2949: 3218 | 3238