> -----Original Message-----
> From: Peter Stuge [mailto:peter_at_stuge.se]
> Sent: Friday, May 07, 2010 12:32 AM
> To: Xu, Qiang (FXSGSC)
> Cc: libcurl development
> Subject: Re: Reflection for Secure IT Server
>
> This is a good idea! You may want to alert them to the fact
> that any SSH implementation MUST support 32kb packets in the
> SSH transport layer, in order to be standards compliant and
> be usable with other SSH implementations.
>
> --8<-- RFC 4253 The Secure Shell (SSH) Transport Layer
> Protocol 6.1. Maximum Packet Length
>
> All implementations MUST be able to process packets with an
> uncompressed payload length of 32768 bytes or less and a
> total packet
> size of 35000 bytes or less (including 'packet_length',
> 'padding_length', 'payload', 'random padding', and 'mac'). The
> maximum of 35000 bytes is an arbitrarily chosen value that
> is larger
> than the uncompressed length noted above. Implementations SHOULD
> support longer packets, where they might be needed.
> -->8--

Thanks a million, Peter! It's great to know RFC4253 explicitly specifies this. :-)

In the mean time, libcurl's maximum packet length CURL_MAX_WRITE_SIZE is defined to be 16KB (16,384 bytes). Can I say it also deviates from the spec? Should this constant be changed to 32768, instead?

Yours Gratetully,
Xu Qiang
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2010-05-07