similar to: md5sum -c failing on some files after rsync backup

I don't know if this has been requested before, but I would really like for rsync to compute an md5sum for each file at the source and destination (with a flag turned off by default of course), and it would realize that I renamed files at the source by noticing a matching md5sum between different filenames It would then rename the destination instead of deleting it and resending the entire

Hi, The release announcement for OpenSSH 4.0p1 had an incorrect md5sum for the portable tarball. The correct md5 is below, otherwise you may verify the integrity of the release using the PGP signature, contained in the file "openssh-4.0p1.tar.gz.sig" in the release directory. MD5 (openssh-4.0p1.tar.gz) = 7b36f28fc16e1b7f4ba3c1dca191ac92 Apologies for any confusion, Damien Miller

There are known Collision Attacks for the MD5SUM method of hashing, so it is possible to modify a file and make it have the same MD5SUM as another file. See this link for details on Collision Attacks: http://en.wikipedia.org/wiki/Collision_attack Recommendation from the US-CERT concerning MD5SUM hashes: http://www.kb.cert.org/vuls/id/836068 Based on the above information, the CentOS team will

There are known Collision Attacks for the MD5SUM method of hashing, so it is possible to modify a file and make it have the same MD5SUM as another file. See this link for details on Collision Attacks: http://en.wikipedia.org/wiki/Collision_attack Recommendation from the US-CERT concerning MD5SUM hashes: http://www.kb.cert.org/vuls/id/836068 Based on the above information, the CentOS team will

Their is no 3.5 server iso posted yet, and their is no md5sum listed for the 3.4 server iso that is posted. Regards, Ted Final Release md5sums (Post 7th June 2005) 81be21fa53cd321a401575def5d0129b CentOS-3.5-i386-disc1.iso 58b0b6b6fa71b328ed2c6c915752f5b0 CentOS-3.5-i386-disc2.iso e7bf5fc1e8b085d536c02dcf581623f3 CentOS-3.5-i386-disc3.iso 27723707d72e83d767495ee0401ec706

Hi, If I do an md5sum across 4 machines all running Centos5-x86_64 on /bin/bash why does it show a different checksum ? -> ssh box4 md5sum -b /bin/bash 53d2152059125e221a38099369e5777e */bin/bash -> ssh box6 md5sum -b /bin/bash e22fb934b0a4a840a330f47559d27205 */bin/bash -> ssh box5 md5sum -b /bin/bash 34bd0269a3ca9ce15e3bf56957d95609 */bin/bash -> ssh box2 md5sum -b /bin/bash

Hello, when I download python-slip-dbus-0.2.20-1.el6_2.noarch.rpm from CentOS 6.5 repository the md5sum is different than when I download same file from 6.4. wget http://msync.centos.org/centos-6/6.5/os/x86_64/Packages/ python-slip-dbus-0.2.20-1.el6_2.noarch.rpm -O python-slip-dbus-0.2.20-1.el6_2.noarch.rpm.65 wget http://msync.centos.org/centos-6/6.4/os/x86_64/Packages/

At our lab we have 200 clients which are mounting to samba share. On some clients a certain file has a different checksum than the others. This is causing many problems because this file is a configuration file. How is this possible? Why aren't some clients taking affect and some are? TIA

I get c1279b77fcccf40379f59a83523a440e *R-2.2.0-win32.exe but I see e8bdf765fe8013129045314c8e2605fd *rw2011.exe on several USA mirrors. I hope the latter is merely in need of a replacement and not an indication of a problem with the web sites. Chuck Charles C. Berry (858) 534-2098 Dept of Family/Preventive Medicine E

I've reproduced on ubuntu and winodws with R3.4.3 When the filepath contains a tilde, the result is NA. But if the file path is expanded then the function works. Example: tools::md5sum("~/.Rprofile") returns NA tools::md5sum(normalizePath("~/.Rprofile")) returns the proper md5 Perhaps this is expected behaviour because the documentation does say NA is returned for

Hello everyone. Thanks to everyone who made this project possible. This is my first post, although I have looked at the archives. I haven't found an answer to this in the archives, so I thought I would post it here. I've downloaded the DVD iso for CentOS-3.1 from BitTorrent, and I'm leaving my torrent open for another day or so to help out. I see there is an MD5Sum file for the

Does anyone know in centos how to create an md5sum list based on the current rpms that I have installed right now on my box? I tried something like rpm -q -v | md5sum >> list but didnt work. Andrew

The tools package is not for users, it's for functions that R uses in installing packages, checking them, etc. If you want a function for users, it would belong in utils. But what's wrong with the digest package? What's the argument that R Core should take this on? Duncan Murdoch On 01/05/2020 5:00 p.m., D?nes T?th wrote: > > AFAIK there is no hashing utility in base R

Perhaps use the digest package? Isn't "R the R packages?" > On May 1, 2020, at 2:00 PM, D?nes T?th <toth.denes at kogentum.hu> wrote: > > > AFAIK there is no hashing utility in base R which can create hash digests of arbitrary R objects. However, as also described by Henrik Bengtsson in [1], we have tools::md5sum() which calculates MD5 hashes of files.

I have a server that is undergoing some patching soon and would like to make note of any files that have changed after the patching is complete. Can you recommend a tool that uses md5sum snapshots to do a quick before and after test, showing anything that's changed on a particular file system?

Hi, To test corruption detection and repair, we modified a file inside the brick directory on server glusterfs1, and scheduled regular scrubs. The corruption is detected: Error count: 1 Corrupted object's [GFID]: 9be5eecf-5ad8-4256-8b08-879aecf65881 ==> BRICK: /data/brick1/gv0 path: /prd/drupal-files-prd/inline-images/small - main building 1_0.jpg We have self-healing enabled, and

Hi all, A friend of mine gives me a copy of Centos5 DVD. I then make an iso of it using dd if=/dev/cdrom of=centos5.iso command. I then check it using sha1sum. But the result is different than of listed in Centos website. Should it the same? Or we simply cannot compare sha1sum from burned DVD to that of 'unburned' iso file? Thanks. -- Fajar Priyanto | Reg'd Linux User #327841 | Linux

tools::md5sum gives a warning if it receives a directory as an argument on Unix but not on Windows. >From what I understand, this happens because in Windows a directory is not treated as a file so fopen returns NULL. Then, NA is returned without a warning. On Unix, a directory is treated as a file so fopen does not return NULL so md5 is run and fails, leading to a warning. This is a good

On 5/1/20 11:09 PM, John Mount wrote: > Perhaps use the digest package? Isn't "R the R packages?" I think it is clear that I am aware of the existence of the digest package and also of other packages with similar functionality, e.g. the fastdigest package. (And I actually do use digest as I guess 99% percent of the R developers do at least as an indirect dependency.) The point

On Sep 8, 2006, at 5:58 AM, Thorsten Sandfuchs wrote: > hio, > as I have some huge files to distribute and md5-sum-checking takes > SOME time > for them, I''m trying to switch to mtime/timestamps, but got no > luck. Regularly > the mtime seems to change and additionally the md5sums generate > themselves > anyway. I''m pretty sure that the file