tomaswolf commented on issue #749: URL: https://github.com/apache/mina-sshd/issues/749#issuecomment-2850301432
Yes, RFC 4253 requires all SSH implementations to handle packets up to 35000 bytes, and recommends that larger packets should be handled, too. Apache MINA sshd and OpenSSH can handle packets up to 256kB on reception. I suppose you're trying to send larger packets for data transfer? In a channel, it's the receiver who says what packet size it requires. See [RFC 4254, section 5.1](https://datatracker.ietf.org/doc/html/rfc4254#section-5.1) So when you open a channel you'd have to two things: 1. Send with the SSH_MSG_CHANNEL_OPEN request a larger maximum packet size (for instance, 256kB, or maybe a little smaller, say, 254kB). (Might make sense if you're mostly receiving data, like downloading something. It doesn't guarantee that the sender will send such large packets, though, it just says that the client will accept packets up to 254kB. The sender might still decide to send smaller packets.) 2. Make the receiver use a larger packet size in its SSH_MSG_CHANNEL_OPEN_CONFIRMATION reply. Might make sense if you want to send a lot of data (uploading), but needs cooperation from the receiver. For Apache MINA sshd, the packet size can be defined via `CoreModuleProperties.MAX_PACKET_SIZE`. I don't know how you'd configure it on the receiver's end if it isn't an Apache MINA sshd implementation. I'm not aware of any SSH protocol extension to re-negotiate the packet size for a channel after the channel has been opened. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
