similar to: Rsync 2.6.6 released

There has been some talk about a zlib security problem that could let someone overflow the buffers in the zlib decompression code, potentially allowing someone to craft an exploit to execute arbitrary code. Since this is a decompression bug, this can only affect an rsync daemon if it allows uploads with the --compress option enabled. If you run a daemon that allows uploads, you may wish to add

There has been some talk about a zlib security problem that could let someone overflow the buffers in the zlib decompression code, potentially allowing someone to craft an exploit to execute arbitrary code. Since this is a decompression bug, this can only affect an rsync daemon if it allows uploads with the --compress option enabled. If you run a daemon that allows uploads, you may wish to add

I have released rsync version 2.6.5. This is primarily a bug-fix release to squash some annoying problems that made it into the (feature-filled) release of 2.6.4, plus a few minor enhancements. Here is a list of the changes between 2.6.4 and 2.6.5: http://rsync.samba.org/ftp/rsync/NEWS The latest man pages are online in their usual spots: http://rsync.samba.org/ftp/rsync/rsync.html

I have released rsync version 2.6.5. This is primarily a bug-fix release to squash some annoying problems that made it into the (feature-filled) release of 2.6.4, plus a few minor enhancements. Here is a list of the changes between 2.6.4 and 2.6.5: http://rsync.samba.org/ftp/rsync/NEWS The latest man pages are online in their usual spots: http://rsync.samba.org/ftp/rsync/rsync.html

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

I believe I have encountered a nasty bug with rsync 2.6.6 "--delete-excluded" option. When this is enabled, rsync''s operation appears to break entirely. I have a script that I''ve been using for a few years. The script hasn''t changed in the last year or so. Recently I upgraded from SuSE 9.3 to SUSE 10.0 which means that I went from rsync 2.6.3 (+ patches,

Josh Coalson wrote: > I've been thinking about this, and here's what I > came up with. This kind of dovetails into the > discussion Mike Wren started about the etree > header. > > I was thinking about defining a FREEFORM metadata > block which may be of arbitrary size. The only > mandatory field would be a (say, 32-bit) id of > the owner. In your case, you

I have released rsync version 2.6.5pre2 -- the second (and hopefully final) pre-release for 2.6.5. The 2.6.5 release is primarily a bug-fix release to squash some annoying bugs that made it into 2.6.4, though a few minor enhancements did make it in as well. To see all the changes since 2.6.4, go here: http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.5pre1-NEWS To read the pre-release man

I have released rsync version 2.6.5pre2 -- the second (and hopefully final) pre-release for 2.6.5. The 2.6.5 release is primarily a bug-fix release to squash some annoying bugs that made it into 2.6.4, though a few minor enhancements did make it in as well. To see all the changes since 2.6.4, go here: http://rsync.samba.org/ftp/rsync/preview/rsync-2.6.5pre1-NEWS To read the pre-release man

I've released rsync 2.6.4pre4. I believe that this version will be what gets released as 2.6.4, hopefully on Wednesday. Please try this out and let me know if anything is amiss. All the changes since 2.6.3 are mentioned here: http://rsync.samba.org/ftp/rsync/preview/NEWS You'll also find a preview of the man pages in the same dir (as usual):

I've released rsync 2.6.4pre4. I believe that this version will be what gets released as 2.6.4, hopefully on Wednesday. Please try this out and let me know if anything is amiss. All the changes since 2.6.3 are mentioned here: http://rsync.samba.org/ftp/rsync/preview/NEWS You'll also find a preview of the man pages in the same dir (as usual):

Howdy, I was playing around with the malloc/free D script provided by Philip Beevers: http://www.opensolaris.org/jive/thread.jspa?threadID=4224&tstart=15 And decided to change the free:entry probe from: pid24169::free:entry / sz[arg0] / { printf("Freeing %p (size %d)\n", arg0, sz[arg0]); sz[arg0] = 0; } to: pid24169::free:entry / ! sz[arg0] / { printf("[ *

Hi all, I upgrade my rsync from 2.3.1 to 2.6.6 today in the client host, everything seems not working after the migration. I didn't touch the rsync server. Herewith is the log from my rsync server. I looks like something related to IPV6, anyone has any idea? Rsync Server : RHEL4 with rsync 2.6.3 deamon running Rsync Client (merlin) : Solaris 8 with rsync 2.6.6 2006/05/09 16:18:40 [5332]

https://bugzilla.samba.org/show_bug.cgi?id=3168 Summary: --min-size cores in 2.6.5 and is completely missing in 2.6.6 Product: rsync Version: 2.6.6 Platform: All OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi, I'm having difficulty configuring Printing with Samba 2.2.4 and Windows 2000 clients. The samba installations is running as a PDC against LDAP. All the sharing of network file systems seem to be working perfectly.. I have a share [printers] path = /usr/spool/samba guest ok = yes printable = yes browsable = no guest ok = yes writable =

https://bugzilla.samba.org/show_bug.cgi?id=2957 Summary: rsync hangs when client put files to server (checked in 2.6.6 too) Product: rsync Version: 2.6.5 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

On Mon, Jan 15, 2018 at 6:20 AM, Randall S. Becker <rsbecker at nexbridge.com> wrote: > Incompatibility introduced at 3.1.3pre1. These are not present at master, > which compiles cleanly. > The master branch and 3.1.3pre1 were pretty much the same until just a moment ago (except that the tar files get some generated files that aren't present in git, such as the autoconf

https://bugzilla.samba.org/show_bug.cgi?id=3029 Summary: rsync 2.6.6 with acl patch compile fails Product: rsync Version: 2.6.5 Platform: All OS/Version: Solaris Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

https://bugzilla.samba.org/show_bug.cgi?id=2957 ------- Additional Comments From sur3857@gmail.com 2005-11-02 18:28 ------- Think I am having the same problem. Sometimes the backup is done, sometimes not. Restarting rsync daemon seems to stops this error from appearing. I am using cwrsync server and client. - cwrsync version, 2.6.6 (also happens with 2.6.5). - rsync daemon running without

Hi all, Reading the wikipedia page on R, I stumbled across the following: http://fluff.info/blog/arch/00000172.htm It does seem interesting that the C execution is that much slower from R than from a native C program. Could any of the more technically knowledgeable people explain why this is so? The author also have some thought-provoking opinions on R being no-good and that you should write