[rsync-announce] Rsync 3.0.2 released w/xattr security fix (attn: 2.6.9 onward)
I have released rsync 3.0.2. This is a security release to fix a potential buffer overflow in the extended attribute support. For more details, see the rsync security advisory page: http://rsync.samba.org/security.html There is a patch there that can be applied to 2.6.9 (if you were using the xattrs.patch), 3.0.0, or 3.0.1. Those running a writable rsync daemon can opt to refuse the xattrs option in their daemon config to avoid the problem without an upgrade. I would like to thank Sebastian Krahmer for bringing this bug to my attention. To see the brief summary of the changes since 3.0.1, visit this link: http://rsync.samba.org/ftp/rsync/src/rsync-3.0.2-NEWS You can download the source tar file and its signature from here: http://rsync.samba.org/ftp/rsync/src/rsync-3.0.2.tar.gz http://rsync.samba.org/ftp/rsync/src/rsync-3.0.2.tar.gz.asc ..wayne.. signature.asc Description: Digital signature ___ rsync-announce mailing list rsync-announce@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-announce
Re: rsync installation _error exit code1
Hello Paul Slootmanevery one, Here i am trying to install rsync3.0.1 on HP-UNIX machine. i have downloaded the source rsync-3.0.1.tarrsync-patches-3.0.1.tar from rsync website. After that i have executed the ./configure, it got executed it displayed message as rsync 3.0.1 configuration successful. In Makefile.in i have changed environment variable [EMAIL PROTECTED]@ to [EMAIL PROTECTED]/local/bin/gcc. after executing the make command i am getting the following error = inccishh0125 703: make config.status: creating Makefile config.status: creating lib/dummy config.status: creating zlib/dummy config.status: creating popt/dummy config.status: creating shconfig config.status: creating config.h config.status: config.h is unchanged Makefile updated -- rerun your make command. Make: Cannot load exit. Stop. *** Error exit code 1 Stop. here i am attatching the installation log. could u pls let me know the problem why make was unable to load gcc. it's very urgent can somebody suggest the solution. with warm regards, mannam srinivas On 4/7/08, Paul Slootman [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Mon 07 Apr 2008, sri vasulu wrote: Hello Paul Slootman, Thank you very much for your suggestion, In my machine i had cc compiler , it seems to be older version.Is it necessary to use GNU C compiler to install rsync or can i proceed with latest version of CC compiler. As long as it's a real C compiler that understands ANSI C, then it should work. However, it may be easier to use GCC. You could also simply use a precompiled rsync version, eg. from http://hpux.cs.utah.edu/hppd/hpux/Networking/Admin/rsync-2.6.9/ (although it is an older version). You can probably also download GCC (and its dependencies) from there. Paul Slootman rsync_installation.log Description: Binary data -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: newbie: rsync 2.6.x problems Cygwin client -- RedHat server
On Mon 07 Apr 2008, S.A. Birl wrote: On Apr 7, 2008, Paul Slootman ([EMAIL PROTECTED]) typed: Paul: On Mon 07 Apr 2008, S.A. Birl wrote: Paul: Paul: Server is running rsync 2.6.1 on RH Paul: Client is running rsync 2.6.3 on Cygwin (Win2003) Paul: Paul: When I connect client to server, I get kicked out after SSH Paul: authentication. I can manually ssh into the server with no problems. Paul: Paul: Is the server running an rsync daemon? If so, why the ssh? Well, unless I misunderstood the man page, I thought I *had* to have another protocol (ssh, ftp, etc) for the rsync daemon. You generally run rsync over ssh, with the following syntax: rsync [options] srcdir remotehost:destdir (pushing to remote host) rsync [options] remotehost:srcdir destdir (pulling from remote host) You can also run a daemon on a host, in which case you can let rsync talk directly to the remote rsync daemon, without ssh: rsync [options] srcdir remotehost::modulename rsync [options] remotehost::modulename destdir Note the double colon instead of a single colon; alternatively: rsync [options] srcdir rsync://remotehost/modulename etc. The modulename can have a subdirectory appended, or a file, etc. One less protocol would be good. How will that affect authentication? Read the manpage for rsyncd.conf and search for secrets file. CONFIDENTIALITY STATEMENT: The information contained in this e-mail, including attachments, is the confidential information of, and/or is the property of, Temple University. The information is intended for use solely by the individual or entity named in the e-mail. If you are not an intended recipient or As mailing lists are open to the entire world eg. via online archives, the intended recipient is the world, so what's the point... If such a footer is forced by your organization, consider getting a gmail account for mailing lists, it's also very useful for searching. Paul Slootman -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Lower-case filenames on receiver side
On Tue, Apr 08, 2008 at 10:16:05AM +0200, Marco Bridge wrote: I mean, rsync seems to be arbitrarily changing filenames No, rsync doesn't change filesnames at all. You should be looking for external reasons for the inconsistencies, such as inconsistent case in the source filename arguments (when combined with a case-ignoring filesystem), the copying from a case-honoring filesystem to a case-ignoring filesystem with overlapping directory names, and/or behind-the-scenes filesystem re-mapping of names. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Lower-case filenames on receiver side
Thanks for your answer, i just learned case-preserving and case- sensitive are two different things... The source partition on my mac is case sensitive the problem is probably the target FAT partition on linux. Now that i think of it, my other backup that goes to an ext3 partition on the same machine does not have this problem. It's still strange that for all other files in the same sync it works fine... Thanks for your answers Marco On 8 Apr, 2008, at 16:33 , Kyle Lanclos wrote: You are going from a case-insensitive filesystem (HFS or HFS+) to a case-sensitive one on the Linux host. If the Mac is inconsistent about how it reports the filename, I can see how you might have problems like what you describe. I am not intimately familiar with problems of this type, as I stay away from case-insensitive filesystems as much as possible. While the inconsistent behavior is strange, I wouldn't be surprised if the root cause is buried somewhere in Apple's filesystem code. --Kyle On 8 Apr, 2008, at 16:34 , Wayne Davison wrote: On Tue, Apr 08, 2008 at 10:16:05AM +0200, Marco Bridge wrote: I mean, rsync seems to be arbitrarily changing filenames No, rsync doesn't change filesnames at all. You should be looking for external reasons for the inconsistencies, such as inconsistent case in the source filename arguments (when combined with a case-ignoring filesystem), the copying from a case-honoring filesystem to a case-ignoring filesystem with overlapping directory names, and/or behind-the-scenes filesystem re-mapping of names. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Rsync 3.0.2 released w/xattr security fix (attn: 2.6.9 onward)
I have released rsync 3.0.2. This is a security release to fix a potential buffer overflow in the extended attribute support. For more details, see the rsync security advisory page: http://rsync.samba.org/security.html There is a patch there that can be applied to 2.6.9 (if you were using the xattrs.patch), 3.0.0, or 3.0.1. Those running a writable rsync daemon can opt to refuse the xattrs option in their daemon config to avoid the problem without an upgrade. I would like to thank Sebastian Krahmer for bringing this bug to my attention. To see the brief summary of the changes since 3.0.1, visit this link: http://rsync.samba.org/ftp/rsync/src/rsync-3.0.2-NEWS You can download the source tar file and its signature from here: http://rsync.samba.org/ftp/rsync/src/rsync-3.0.2.tar.gz http://rsync.samba.org/ftp/rsync/src/rsync-3.0.2.tar.gz.asc ..wayne.. signature.asc Description: Digital signature -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync 3.0.2 released w/xattr security fix (attn: 2.6.9 onward)
On Apr 8, 2008, at 12:53 PM, Wayne Davison wrote: I have released rsync 3.0.2. This is a security release to fix a potential buffer overflow in the extended attribute support. For more details, see the rsync security advisory page: http://rsync.samba.org/security.html There is a patch there that can be applied to 2.6.9 (if you were using the xattrs.patch), 3.0.0, or 3.0.1. Thanks Wayne, I only use the fileflags and crtimes patches. Can I just use them from the patch files directory released with 3.0.1, on 3.0.2? Rob Those running a writable rsync daemon can opt to refuse the xattrs option in their daemon config to avoid the problem without an upgrade. I would like to thank Sebastian Krahmer for bringing this bug to my attention. To see the brief summary of the changes since 3.0.1, visit this link: http://rsync.samba.org/ftp/rsync/src/rsync-3.0.2-NEWS You can download the source tar file and its signature from here: http://rsync.samba.org/ftp/rsync/src/rsync-3.0.2.tar.gz http://rsync.samba.org/ftp/rsync/src/rsync-3.0.2.tar.gz.asc ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5380] New: %M in log format converts following spaces into '-'
https://bugzilla.samba.org/show_bug.cgi?id=5380 Summary: %M in log format converts following spaces into '-' Product: rsync Version: 3.0.2 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] Consider rsync -an --out-format=%M %f /home /tmp In the output, all spaces following %M are converted to '-'. (When using tabs to delimit the format specifiers, the problem does not seem to occur.) The same happens when using custom log formats. This is on Linux [Fedora 7, 2.6.21-1.3228.fc7, x86_64, glibc 2.6]. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5380] %M in log format converts following spaces into '-'
https://bugzilla.samba.org/show_bug.cgi?id=5380 --- Comment #1 from [EMAIL PROTECTED] 2008-04-08 19:14 CST --- Created an attachment (id=3252) -- (https://bugzilla.samba.org/attachment.cgi?id=3252action=view) proposed fix (the argument to strchr in log.c seems to be incorrect) -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5380] %M in log format converts following spaces into '-'
https://bugzilla.samba.org/show_bug.cgi?id=5380 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #3252 is|0 |1 obsolete|| --- Comment #2 from [EMAIL PROTECTED] 2008-04-08 19:31 CST --- Created an attachment (id=3253) -- (https://bugzilla.samba.org/attachment.cgi?id=3253action=view) make the previous patch more efficient (don't rescan the already processed string) -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync installation _error exit code1
On Tue, 2008-04-08 at 14:28 +0530, sri vasulu wrote: Here i am trying to install rsync3.0.1 on HP-UNIX machine. i have downloaded the source rsync-3.0.1.tarrsync-patches-3.0.1.tar from rsync website. After that i have executed the ./configure, it got executed it displayed message as rsync 3.0.1 configuration successful. In Makefile.in i have changed environment variable [EMAIL PROTECTED]@ to [EMAIL PROTECTED]/local/bin/gcc. The configure script determines the CC variable for your system (among other variables) and then copies Makefile.in to Makefile, replacing tokens like @CC@ with the appropriate values. The right way to set a variable like CC is on the ./configure command line: ./configure CC=/usr/local/bin/gcc If you insist on modifying Makefile.in, you need to delete the @ sign because it is a marker for the configure script to replace, not part of the makefile syntax. This explains your make install error. after executing the make command i am getting the following error = inccishh0125 703: make config.status: creating Makefile config.status: creating lib/dummy config.status: creating zlib/dummy config.status: creating popt/dummy config.status: creating shconfig config.status: creating config.h config.status: config.h is unchanged Makefile updated -- rerun your make command. Make: Cannot load exit. Stop. *** Error exit code 1 Stop. It looks like something, perhaps your modification to Makefile.in, triggered the rule that updates Makefile. If this happens, do what the message says and run make again. If the same thing keeps happening, you can delete the rule from Makefile. The rule looks like this: Makefile: Makefile.in config.status @./config.status @echo Makefile updated -- rerun your make command. @exit 1 Good luck. Matt signature.asc Description: This is a digitally signed message part -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[SCM] rsync annotated tag, v3.0.2, created. v3.0.2
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project rsync. The annotated tag, v3.0.2 has been created at 2c02677b19a8b6fe87edb3b0973f2b115bb0c978 (tag) tagging 8ba802f3b4968c7c105ea017d0b20d56ec9d5d0f (commit) replaces v3.0.1 tagged by Wayne Davison on Tue Apr 8 08:17:39 2008 -0700 - Log - Version 3.0.2. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBH+4yTbIWfsUuWqMURAiVgAKCKirl7KEy5PIqXYH3T+FfiSV5TgwCfb9BA EpVF88j5emEYQ7rxk8aic68= =IXwm -END PGP SIGNATURE- Wayne Davison (9): Bump the repository version to 3.0.2dev. Fixed the code that removes old file versions for a final release. Comment out the Source1 tar file by default in the spec file. Moving some files from support into packaging. Have the spec file put more useful stuff into the doc dir. Fixed a potential overflow issue with realloc() that Sebastian Krahmer Roll over the NEWS files for the next release. Call patch-update in its new location. Preparing for release of 3.0.2 --- hooks/post-receive -- rsync ___ rsync-cvs mailing list rsync-cvs@lists.samba.org https://lists.samba.org/mailman/listinfo/rsync-cvs
