similar to: definite data corruption in 2.5.0 with -z option

Hi. When I discovered rsync, it immediately became one of my most indispensable utilities. It's a real godsend on bandwidth-limited links, especially digital cellular. It works remarkably well in the general case, but I think the algorithm could be improved for one very important special case. Many (or even most) of the updated files I transfer with rsync change only by stuff being appending

Is anyone else concerned about the fact that rsync doesn't guarantee to produce identical file copies on the the target machine? Don't get me wrong in sounding critical because I think that rsync is a great example of how software should be written. (I often make the observation, as I learn more about Linux, and inevitably find myself comparing open source applications to Microsoft

Hi folks, This applies to src/share/man/man5/moduli.5 in the OpenBSD source tree, and doesn't seem to apply to the portable OpenSSH, so I've sent this change here instead of via Bugzilla. The wording of moduli(5) implies that sshd puts more thought about which modulus it selects than it really does. The following patch corrects this. Simon. -- Simon Burge

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 openssh-1.2.1pre20 has been released at: http://violet.ibs.com.au/openssh/files/ This release integrates more of Andre Lucas' portability patch, Ben Taylor's utmpx patch and some cleanups and bugfixes of my own. The auth-passwd failures should be fixed, as should lastlog support on NetBSD. Since Andre Lucas' patch included platform

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 openssh-1.2.1pre20 has been released at: http://violet.ibs.com.au/openssh/files/ This release integrates more of Andre Lucas' portability patch, Ben Taylor's utmpx patch and some cleanups and bugfixes of my own. The auth-passwd failures should be fixed, as should lastlog support on NetBSD. Since Andre Lucas' patch included platform

Does rsync work over an NFS mount? --Karl _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

I am trying to rsync a file of 10gb between an NT host running Cygwin 4.10 and a Solaris 8 host running rsync 2.5.1 but am having problems with what appears to be a 2gb file limit - the truncation point occurs at 2096111616 bytes. The target filesystem definately supports files over 2GB. Any ideas how to overcome this limitation? Regards, Craig Donnelly Andel Consulting 10 Fenchurch Avenue

What is the default block size? I have a few files 30+mb and data is just added to the end of them. It seems like it takes longer to sync them that it was to send it initially. Should I change the block size or something else? I am running: rsync -z -e ssh *.* user@linuxbox:data/ I need to use ssh because I am going over the internet and sending "company data". -------------- next

FYI, We've been using the 2.4.7pre1 release for several days now, with nary a hang problem. We haven't seen the EOF bug at all, which was what we upgraded for. This is with transfers of as much as 50GB to set up an initial mirror. The only thing we did was set timeout=0 -- which I guess is unnecessary. The semantics of this flag are a bit unclear. We thought was 'time since

I am having trouble with rsync when I am trying to synchronize a Windows NT volume mounted with smb_fs (FreeBSD) and a unix volume which is also exported with Samba. There are instances where the DOS short name on the NT volume ends up as upper case and then doesn't match filenames which are used in the unix volumes which have been exported by Samba. I don't know if this is a Samba

Hello, Recently while working with rsync as the way to mirror large (several GB) archive on a regular basis, I came across several problems, and also got the ideas about their possible solutions - please could you investigate & consider implementing the features, described below, to future RSYNC releases ? - when the checksumming (consider very large archive, several GB) stage of rsync

Scenario: Use the ssh-keygen utility in openssh-1.2pre17 to generate a host key Kill and restart sshd Remove the old host key from ~/.ssh/known_hosts Connect to the host using ssh. I get this: homer.ka9q.ampr.org$ ssh 199.106.106.3 who The authenticity of host '199.106.106.3' can't be established. Key fingerprint is 1024 a0:8d:17:f0:fa:a9:9f:6f:b5:d0:1c:d6:02:92:bd:5e. Are you sure

I recently installed rsync 2.5.5 on both my rsync server and client being used. I installed the latest version because I was having problems with rsync stalling with version 2.4.6 (I read that 2.5.5 was supposed to clear this up or at least give more appropriate errors). I am still having problems with rsync stalling even after upgrading to 2.5.5. It only stalls in the "/home" tree

CentoOS 7 python-cryptography package is at version 0.8.2 It has a build-requires for python-cryptography-vectors of the same version (but different source tarball apparently) There is no python-cryptography-vectors in CentOS 7 base or updates. There is one in EPEL but it is version 0.8 -=- If you relax the BuildRequires to just require python-cryptography-vectors then the build fails

There were a few notes in this thread that may indicate open areas for development. I forward merely as FYI. http://www.metzdowd.com/pipermail/cryptography/2015-January/024231.html ---------- Forwarded message ---------- From: Peter Gutmann <pgut001 at cs.auckland.ac.nz> Date: Sun, Jan 4, 2015 at 9:29 PM Subject: Re: [Cryptography] Why aren?t we using SSH for everything? To: calestyo at

Hi, Does rsync lock the source files while its copying? Any input is appreciated. Thank you Dietrich

If I run the following command: # /usr/local/bin/rsync -a --stats -v --delete --force --recursive /source /dest building file list ... done source/file1 source/file2 source/file3 source/file4 source/file5 source/ Number of files: 74 Number of files transferred: 5 Total file size: 1104726340 bytes Total transferred file size: 115163136 bytes Literal data: 463500 bytes Matched data: 114699636

Hi all, while fiddling with VmWare View without being able to join windows7 client to samba4 domain, we stumbled on the following article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1028164 which says, should we run MS Windows 2008R2 AD, we should enable the "Allow cryptography algorithms compatible with Windows NT 4.0"

Hello, I have compiled rsync 2.5.0 cleanly on a Solaris 2.6 box, and can use the resultant binary as a client with no problem. However, when I try and start a daemon, it exits with exit code 0, and no daemon running. I have previously run 2.4.6 and other versions with the same rsyncd.conf file, but can't seem to get the daemon up with 2.5.0. A truss shows the following: # truss -f

Hi folks. FYI: There's a discussion[0] about keystroke timing attacks against SSH going on on the cryptography mailing list. Would be interesting to hear the opinion of some OpenSSH folks what SSH/OpenSSH is doing against this and what could maybe be don in addition. Especially since the main idea behind the attack is obviously not limited to the initial authentication phase when a password