Re: rsync 2.6.6pre1 released (ALERT: info on zlib security flaw)

2005-07-09 Thread Dmitry V. Levin
On Fri, Jul 08, 2005 at 02:10:19PM -0700, Wayne Davison wrote: [I neglected to cross-post this from the rsync-announce list to the regular rsync mailing list when I sent this out yesterday.] There has been some talk about a zlib security problem that could let someone overflow the buffers in

Re: Restricting rsync over ssh

2004-12-28 Thread Dmitry V. Levin
Hi, On Tue, Dec 28, 2004 at 04:53:45PM +0100, Bob wrote: I have very special needs and i wanted to use rsync over ssh. I don't know if a solution already exists for what i want to do. I want to provide rsync over ssh to my users. Howevern i want to have the following limitations : 1. No

Re: Restricting rsync over ssh

2004-12-28 Thread Dmitry V. Levin
On Tue, Dec 28, 2004 at 05:24:27PM +0100, Bob wrote: I would like to avoid using chroot because it implies my dummy-shell must run in suid root. Furthermore, it forces to create a jail with the binaries and libraries inside. I was thinking to this solution to avoid doing this. Is there any

Re: rsync and broken symlinks

2004-12-16 Thread Dmitry V. Levin
Hi, On Thu, Dec 16, 2004 at 01:07:35AM -0800, Wayne Davison wrote: On Thu, Dec 16, 2004 at 01:38:42PM +0500, Yakov Hrebtov wrote: where is the message -- skipping non-regular file broken-link? I can only imagine that this is some kind of OS misfeature. Try running rsync under something

Re: rsync and broken symlinks

2004-12-16 Thread Dmitry V. Levin
Hi, On Thu, Dec 16, 2004 at 09:02:24AM -0800, Wayne Davison wrote: On Thu, Dec 16, 2004 at 02:34:02PM +0500, Yakov Hrebtov wrote: You see, readlink call is successful. But rsync then trying to access the referent of symlink... But referent doesnt exist. The only time that rsync calls

Re: rsync and broken symlinks

2004-12-16 Thread Dmitry V. Levin
Hi, On Thu, Dec 16, 2004 at 10:27:20PM +0100, Paul Slootman wrote: On Thu 16 Dec 2004, Wayne Davison wrote: As for the fix, one could argue that ignore nonreadable has a bug in it when dealing with symlinks -- if readlink() worked, the symlink was readable, so there is no need to call

Re: patch for replacing non-printable chars in filenames

2004-11-23 Thread Dmitry V. Levin
Hi, On Tue, Nov 23, 2004 at 05:29:57PM +0100, Paul Slootman wrote: There's a bug reported in Debian about the tty being screwed up by wierd filenames, see http://bugs.debian.org/bug=242300 On the one hand, find will also do this. On the other hand, ls will replace such chars with a question

Re: 2.6.2 rsync --daemon is not working for me

2004-10-27 Thread Dmitry V. Levin
On Tue, Sep 28, 2004 at 08:55:33AM -0700, Wayne Davison wrote: On Tue, Sep 21, 2004 at 12:37:55PM +0500, Sergey Golovin wrote: I'm unable to write with remote rsync in daemon mode. The strace you included shows that it is the fork() call that is returning -1 (EAGAIN). So, you need to

*****SPAM***** I: rsync --delete is unable to handle broken symlinks properly

2002-07-16 Thread Dmitry V. Levin
SPAM: Start SpamAssassin results -- SPAM: This mail is probably spam. The original message has been altered SPAM: so you can recognise or block similar unwanted mail in future. SPAM: See http://spamassassin.org/tag/ for more details. SPAM: SPAM: Content