search for: baarda

...ed. To defeat the k-bit truncated MD4 checksum2, just keep generate random blocks having the same checksum1 until you find two with the same checksum2; by the birthday paradox it will take about 2^(k/2) attempts, where usually k=16 or k=24 with J.W. Schultz's code. Another note is that Donovan Baarda's formula for the probability of retransmission (and thus J.W. Schultz's code) assumes that the hashes are random. This is a reasonable assumption for the truncated MD4 checksum2 when checksum_seed is random, but it's a pretty rotten assumption for the Fletcher checksum1. For the purpos...

Dear guru's Hopefully someone can shed some light in my issue. I have created a queue with a ringall strategy and all works fine. I want a caller to be able to exit the queue so they can leave a message. I've added the H option in queue command so callers can press * to exit. So far all well, on the cli there is a message the caller pressed * and the extensions stops ringing. But

On Thu, 2004-04-08 at 12:36, Martin Pool wrote: > On 5 Apr 2004, Donovan Baarda <abo@minkirri.apana.org.au> wrote: > > > librsync needs a whole file checksum. Without it, it silently fails for > > case 1), 3), and 4). > > Yes, a whole-file checksum should be used with it. Presumably > something stronger than md4 like SHA-1. md4 is probably goo...

Hi, Is there a way in which rsync's -z compression (zlib) utility can be benchmarked? I'm trying to compare the compression ratio between rsync and external compression tools like gzip and bzip2. Are there any advantages to using rsync's internal compression mechanism specified with the -z option compared to solely applying external compression i.e. bzip2 to the files and invoking

Hi, while implementing the rsync protocol in one of our projects I found that the current CVS version still has a MD4 bug. I'm using the FreeBSD libmd implementation and I still had checksum mismatches with protocol version 27 for files whose size was a multiple of 64 - 4 ( - 4 due to checksum_seed). A patch for todays CVS version is attached. Someone should also review the clean_fname()

Hi Donovan, Thank you for the insight. I will keep you posted on this. Best Regards Naveen A. >From: Donovan Baarda <abo@minkirri.apana.org.au> >To: Naveen Athresh <naveenathresh@hotmail.com> >CC: rsync@samba.org,librsync developers list ><librsync-devel@lists.sourceforge.net> >Subject: Re: rsync - windows how should I compile the code any clues >-Thanks ! >Date: 16 Apr 2003...

...ad by the --*-from options. (Wayne Davison) * Length of csum2 is now per-file starting with protocol version 27. (J.W. Schultz) * Per-file dynamic block size is now sqrt(file length). The per-file checksum size is determined according to an algorithm provided by Donovan Baarda which reduces the probability of rsync algorithm corrupting data and falling back using the whole md4 checksums. (J.W. Schultz, Donovan Baarda) * The --stats option no longer includes the (debug) malloc summary unless the verbose option was specified at least twice. * Ad...

G'day, I've been working on a Python interface to librsync and have noticed that it uses md4sum code borrowed from Andrew Tridgell and Martin Pool that comes via rsync and was originally written for samba. Is there anything special about this code compared to the RSA md4sum code that can be found with libmd <"http://www.penguin.cz/~mhi/libmd/">? Python uses the RSA

I'm not sure if this is the appropriate forum for questions regarding librsync, but couldn't find any others. I'm trying to get librsync working properly on Solaris 2.7 and 2.8 Sparc servers. The problem is that while librsync appears to compile cleanly, "make check" fails the sources.test. Does anyone have any insight as to why this might be? Might I need a specific

Hi, Where can I get good pointers on the rolling checksum algorithm used in rsync? I need an 8-bit or 12-bit rolling checksum too. Any place where "rolling" checksum algorithms are discussed? Seun Osewa ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

What is the general recommendation for compression when using ssh? Is it a wasteful performance hit to have both ssh and rsync do compression (when using rsync over ssh)? If so, is there a clear prefference which is more efficient, rsync or ssh? Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/

Is there any chance for rdiff ? I need to frequently synchronize big text file (60MB+) undertaking small changes and I am interested in differences between the subsequent versions [DNS RBL data in dnsbl format, 1E6+ lines of text, new version every 20m, on average 50 new entries (lines) in every synchronization] I would like to get (small) diff file as result of rsync session and apply it to

Hi, I currently create large (500MB-2.5GB) tar.gz files that I am trying to get to rsync better. After doing some research by reading a lecture presented by the original author of rsync and googling the list archives, I have concluded that the gzip-rsyncable.diff is the best way to get gzipped files to rsync nicely. The only version I could find of this patch is available here:

I'm interested in these very questions (librsync-rsync relationship, remaining limitations of rsync, active prospects for ground-up rewrites), Google searches for rsync info have proved a little too vague due to the programs ubiquity. Much has certainly changed since this was written, could some people with knowledge in these areas could update martin's response for the state of rsync,

Hello! As I was found rsync do not detect file renaming. If I just copy my backup.0.tgz (many Mbytes in size having it's md5) to backup.1.tgz (which will be equial in size and md5) it will be the same file in fact... Rsync will delete old file (backup.0.tgz) on the receiving side and download new one (backup.1.tgz). I do not think there are any difficulties to detect this situation and

Hi, I have a unique issue that I am dealing with here. I need to develop rsync algorithm into a library that can be re-used with my VB / VC application on Windows platform. I need your advice if there is any library already available on the Internet for this? I did get librsync but that is just a header file which I do not know how to compile also with the existing code I have. Can you

...iles larger than 478KB. A 1MB file will have 1024 1KB blocks and a 4GB file would have 65,536 64KB blocks. --block-size will override this regardless of what block size is specified. The variable checksum size takes block size into account using an approximation of the formula provided by Donovan Baarda on this list (blocksum_bits includes the 32bit sum1). blocksum_bits = BIAS + 2*log2(file_len) - log2(block_len) This should result in increased efficiency as files grow, reduce the likelihood of file-redo and raise the ceiling on how large a file can be processed by rsync. The one case wher...

...f use is a major selling point for ghost. > > Options commonly needed for making a ghost image of NTFS are "-ntil" and > "-ntic" which ignore various check done for NT. > > > > *********** REPLY SEPARATOR *********** > > On 12/18/02 at 9:59 AM Donovan Baarda wrote: > >On Tue, 2002-12-17 at 21:13, John Morgan Salomon wrote: > >> Dr. Poo wrote: > >> > Now, can you think of a way to sync the win 2000 OS? (the WHOLE > > > >flippin' > > > >> > system) so that if it were to go down one could restor...

As threatened a while back, there are some exclude/include bugs that I'd like to see fixed in rsync. Here is the patch: http://www.blorf.net/rsync-exclude.patch This fixes the following bugs: - A non-anchored, slash-including pattern with a wildcard needs to be matched at the end of the path (e.g. "CVS/R* should match throughout the tree, not just at /CVS/R*). - A leading

On Tue, 2006-02-21 at 14:58 -0800, rsync2eran@tromer.org wrote: > A year ago we discussed the strength of the MD4 hash used by rsync and > librsync, and one of the points mentioned was that only collision > attacks are known on MD4. Could you please forward this into the bug tracker so it's not lost? -- Martin -------------- next part -------------- A non-text attachment was