search for: outgoing_packet

...nd '%s' disabled (badness %d)", diff -u openssh-2.1.1p1.orig/packet.c openssh-2.1.1p1/packet.c --- openssh-2.1.1p1.orig/packet.c Wed May 17 08:53:35 2000 +++ openssh-2.1.1p1/packet.c Tue Jun 20 16:39:00 2000 @@ -356,7 +356,7 @@ char buf[9]; buffer_clear(&outgoing_packet); - memset(buf, 0, 8); + memset(buf, 0, 9); buf[8] = type; buffer_append(&outgoing_packet, buf, 9); }

...} else { + if ((r = start_compression_zstd_in(ssh)) != 0) + return r; + } + comp->enabled = COMP_ZSTD; + } else { + return SSH_ERR_INTERNAL_ERROR; + } } } return 0; @@ -1104,9 +1300,15 @@ ssh_packet_send2_wrapped(struct ssh *ssh) if ((r = sshbuf_consume(state->outgoing_packet, 5)) != 0) goto out; sshbuf_reset(state->compression_buffer); - if ((r = compress_buffer(ssh, state->outgoing_packet, - state->compression_buffer)) != 0) - goto out; + if (comp->enabled == COMP_ZSTD) { + if ((r = compress_buffer_zstd(ssh, state->outgoing_packet, +...

I added ZSTD support to OpenSSH roughly three years ago and I've been playing with it ever since. The nice part is that ZSTD achieves reasonable compression (like zlib) but consumes little CPU so it is unlikely that compression becomes the bottle neck of a transfer. The compression overhead (CPU) is negligible even when uncompressed data is tunneled over the SSH connection (SOCKS proxy, port

...static int compression_buffer_ready = 0; /* Flag indicating whether packet compression/decompression is enabled. */ static int packet_compression = 0; +#endif /* default maximum packet size */ int max_packet_size = 32768; @@ -233,10 +235,12 @@ buffer_free(&output); buffer_free(&outgoing_packet); buffer_free(&incoming_packet); +#ifdef WITH_COMPRESSION if (compression_buffer_ready) { buffer_free(&compression_buffer); buffer_compress_uninit(); } +#endif } /* Sets remote side protocol flags. */ @@ -255,6 +259,7 @@ return remote_protocol_flags; } +#ifdef WITH_COMP...

I hacked zstd support into OpenSSH a while ago and just started to clean it up in the recent days. The cleanup includes configuration support among other things that I did not have. During testing I noticed the following differences compared to zlib: - highly interactive shell output (as in refreshed at a _very_ high rate) may result in higher bandwidth compared to zlib. Since zstd is quicker

I added ZSTD support to OpenSSH roughly over a year and I've been playing with it ever since. The nice part is that ZSTD achieves reasonable compression (like zlib) but consumes little CPU so it is unlikely that compression becomes the bottle neck of a transfer. The compression overhead (CPU) is negligible even when uncompressed data is tunneled over the SSH connection (SOCKS proxy, port

I'm reading this fine article on O'Reilly: http://linux.oreillynet.com/lpt/a//linux/2001/11/08/ssh_keystroke.html <quote> The paper concludes that the keystroke timing data observable from today's SSH implementations reveals a dangerously significant amount of information about user terminal sessions--enough to locate typed passwords in the session data stream and reduce the

In sshconnect.c there are two global variables for server_version_string client_version_string. These are used just in a few functions and can easily be passed as parameters. Also, there is a strange construct, where their memory is allocated to the global pointers, then copies of these pointers are assigned to the kex structure. The kex_free finally frees them via cleanup of the kex

...(c) + ASC('@')); } else { *dst++ = '-'; *dst++ = c; diff -bur openssh-3.7.1p2.orig/packet.c openssh-3.7.1p2/packet.c --- openssh-3.7.1p2.orig/packet.c Tue Sep 23 11:00:41 2003 +++ openssh-3.7.1p2/packet.c Tue Oct 7 08:22:01 2003 @@ -473,6 +473,18 @@ { buffer_put_int(&outgoing_packet, value); } +#ifdef CHARSET_EBCDIC +void +packet_put_binary(const void *buf, u_int len) +{ + buffer_put_binary(&outgoing_packet, buf, len); +} +void * +packet_get_binary(u_int *length_ptr) +{ + return buffer_get_binary(&incoming_packet, length_ptr); +} +#endif void packet_put_string(const...