Displaying 20 results from an estimated 900 matches similar to: "[Bug 2888] New: Consider adding other compression schemes (lz4, zstd)"
2020 Sep 08
3
[PATCH 0/5] ZSTD compression support for OpenSSH
On 2020-09-07 11:21:13 [+1000], Darren Tucker wrote:
> The zstd part would be a larger discussion because we would need to
> either carry it as a Portable patch or have zstd added to OpenBSD
> base, and I don't know if that would be accepted. Do you have any
> performance numbers for zstd in this application?
A key stroke is here 10 bytes of raw data which zstd compresses usually
2020 Apr 06
6
[Bug 14338] New: ZSTD support
https://bugzilla.samba.org/show_bug.cgi?id=14338
Bug ID: 14338
Summary: ZSTD support
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: core
Assignee: wayne at opencoder.net
Reporter: Rsync at ml.breakpoint.cc
2023 Feb 24
1
[PATCH 0/1] ZSTD compression support for OpenSSH
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
2019 Feb 23
5
[Bug 2972] New: Add build-time option to use OpenSSL for ChaCha20-Poly1305
https://bugzilla.mindrot.org/show_bug.cgi?id=2972
Bug ID: 2972
Summary: Add build-time option to use OpenSSL for
ChaCha20-Poly1305
Product: Portable OpenSSH
Version: 7.9p1
Hardware: ARM
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Miscellaneous
2020 Sep 05
8
[PATCH 0/5] ZSTD compression support for OpenSSH
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
2020 Mar 24
4
ZSTD compression support for OpenSSH
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
2023 Feb 24
1
[PATCH 1/1] Add support for ZSTD compression
From: Sebastian Andrzej Siewior <sebastian at breakpoint.cc>
The "zstd at breakpoint.cc" compression algorithm enables ZSTD based
compression as defined in RFC8478. The compression is delayed until the
server sends the SSH_MSG_USERAUTH_SUCCESS which is the same time as with
the "zlib at openssh.com" method.
Signed-off-by: Sebastian Andrzej Siewior <sebastian at
2020 Aug 06
6
rsync upgrade
On 2020-08-06 08:45, J Martin Rushton via CentOS wrote:
> You'll need to upgrade to CentOS8.
>
> C7 is at rsync 3.1.2-10, and will not go above 3.1.2 ever.
>
> C8.2 is at 3.1.3-7, C8 will always be on 3.1.3
>
> Martin
Another option is to build rsync from source, which is what I did to try
out the zstd compression.
centos7$ rsync --version
rsync? version 3.2.2? protocol
2020 May 21
4
[Bug 14390] New: Feature request: don't fail if using "-z" transferring to rsync complied with --with-included-zlib=no
https://bugzilla.samba.org/show_bug.cgi?id=14390
Bug ID: 14390
Summary: Feature request: don't fail if using "-z" transferring
to rsync complied with --with-included-zlib=no
Product: rsync
Version: 3.1.3
Hardware: All
OS: All
Status: NEW
Severity: enhancement
2020 Aug 28
2
zlib errors after upgrading
ok, I did install zstd (zstd command line interface 64-bits v1.4.4, by
Yann Collet)
reconfigured & compiled dovecot 2.3.10.1 again with option : with-zstd
changed the configuration file to :
zlib_save = zstd
and restarted dovecot -
now I have following log file errors :
Aug 28 16:17:39 lxc-imap dovecot:
imap(rnowotny)<237930><H1kft/CtENRUclcc>: Error: zlib_save: Unknown
2024 Mar 12
1
rsync segfaults when openssl fips is enabled
Hi All,
Any inputs on this issue?
--
Shedi
On Wed, Feb 21, 2024 at 5:12?PM Shreenidhi Shedi <
shreenidhi.shedi at broadcom.com> wrote:
> Hi All,
>
> Copying the content from the GH issue as is.
> Need your inputs on the same.
> FWIW, the coredump files generated in linux have xattr values which are >
> 32 bytes.
>
> https://github.com/WayneD/rsync/issues/569
2015 Nov 25
0
LZ4 mailbox corruption
Hello,
When I look at email files on my server (mdbox format), they contain
random LZ4 stuff. I have now changed the compression to gzip and new
mails look cleaner. But older ones have problems.
A mail file looks like this:
2 M1e C5655b6a8
^A^BN 00000000000006F4
Dovecot-LZ4^M*<9B><C5>^@^A^@^@^@^@^F<DD><FF><83>Return-path:
<nobody at
2020 Oct 12
1
LZ4 Kernel Decompression not supported
I am running XEN on CentOS Linux release 7.8.2003
I have a Debian 7, and two Gentoo DomU Guests running fine.
I am trying to get an Ubuntu 20.04 DomU Guest running but I get this error when trying to run the netboot kernel image
xc_dom_probe_bzimage_kernel unable to LZ4 decompress kernel
I understand that CentOS Xen does not support LZ4 decompression.
Is there a workaround for this?
2020 Feb 06
0
[PATCH] Add support for zstd compression
From: Sebastian Andrzej Siewior <sebastian at breakpoint.cc>
zstd compression was announced as "good compression with high
throughput" so I gave it a try. With zlib, on high speed links the CPU
is usually the bottle neck. With zstd I'm able to fill a 200Mbit link :)
zstd detection happens automatically via pkg-config. No zstd header means
no error about missing zstd. So that
2013 Oct 24
1
LZ4 compression in openssh
I'm a long time user of openssh and I was wondering if there is any work
towards supporting alternative compression methods in openssh like LZ4?
Regards,
Mark
--
Mark E. Lee <mark at markelee.com>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message
2020 Sep 10
2
zlib errors after upgrading to 2.3.11.3
On 9. Sep 2020, at 11.14, Robert Nowotny <rnowotny1966 at gmail.com> wrote:
Sep 3 08:33:25 lxc-imap dovecot: imap(mpaul)<48684><2/9E5mKuAezAqKjk>:
Error: Mailbox Sent: UID=2171:
read(zlib(/home/vmail/virtualmailboxes/mpaul/storage/m.119)) failed:
read(/home/vmail/virtualmailboxes/mpaul/storage/m.119) failed: Broken pipe
(FETCH BODY[])
Also this way you can see if the broken
2013 Oct 25
2
LZ4 compression in openssh
Compression has some problematic interactions with encryption that OpenSSH
seems to have handled far before anyone else (by having it off by default).
On Thursday, October 24, 2013, Darren Tucker wrote:
> On Thu, Oct 24, 2013 at 07:30:38PM -0400, Mark E. Lee wrote:
> > I'm a long time user of openssh and I was wondering if there is any work
> > towards supporting alternative
2020 Aug 06
6
rsync upgrade
Can anyone tell me the repository to use to upgrade to a version of
rsync later than 3.1.2?
Chris
--
Christopher Wensink
IS Administrator
Five Star Plastics, Inc
1339 Continental Drive
Eau Claire, WI 54701
Office: 715-831-1682
Mobile: 715-563-3112
Fax: 715-831-6075
cwensink at five-star-plastics.com
www.five-star-plastics.com
2012 Jul 23
0
[zfs] LZ4 compression algorithm
----- Forwarded message from Bob Friesenhahn <bfriesen at simple.dallas.tx.us> -----
From: Bob Friesenhahn <bfriesen at simple.dallas.tx.us>
Date: Mon, 23 Jul 2012 12:55:44 -0500 (CDT)
To: zfs at lists.illumos.org
cc: Radio m?odych bandyt?w <radiomlodychbandytow at o2.pl>,
Pawel Jakub Dawidek <pjd at FreeBSD.org>, developer at lists.illumos.org
Subject: Re: [zfs] LZ4
2013 Oct 25
0
LZ4 compression in openssh
Thanks for the response, what kind of problematic interactions would
occur (other than trying to compress seemingly random data)?
Regards,
Mark
On Fri, 2013-10-25 at 04:02 -0400, Dan Kaminsky wrote:
> Compression has some problematic interactions with encryption that
> OpenSSH seems to have handled far before anyone else (by having it off
> by default).
>
> On Thursday, October