similar to: Design: Adding checksums to index files

Extend Index_parser.entry to hold a list of checksums to validate, and validate all of them. This does change nothing currently, as only sha512 is read, while still allowing us to fetch more checksums if needed. --- builder/builder.ml | 6 +++--- builder/checksums.ml | 3 +++ builder/checksums.mli | 3 +++ builder/index_parser.ml | 22 +++++++++++++++-------

Move the Checksums module from virt-builder mostly as it is; the only change is that on checksum mismatch an exception is raised rather than invoking "error" directly: this way users of verify_checksum & verify_checksums can do their own handling of the situation. --- builder/Makefile.am | 2 -- builder/builder.ml | 6 +++++- builder/checksums.ml | 57

Introduce a new Checksums module to handle the check of checksums, moving part of the Sigchecker code to it. Adapt the rest of virt-builder to this new module. --- builder/Makefile.am | 2 ++ builder/builder.ml | 2 +- builder/checksums.ml | 51 +++++++++++++++++++++++++++++++++++++++++++++++++ builder/checksums.mli | 29 ++++++++++++++++++++++++++++ builder/index_parser.ml | 4

Hi, when using RSync for mirroring, the checksums of a file are calculated for each transfer. But that causes a lot of CPU/IO load on the server machine and degrades throughput even if there's plenty of network bandwidth. So I want to propose a pre-calculating feature for checksums. The easiest way would be to add a CLI-option like '--pre-checksum' to RSync. That way RSync would just

Make use of the Checksums module to ease the verification of the SHA1 checksums in manifests. --- v2v/input_ova.ml | 17 +++++------------ 1 file changed, 5 insertions(+), 12 deletions(-) diff --git a/v2v/input_ova.ml b/v2v/input_ova.ml index 4f848e2..5731a45 100644 --- a/v2v/input_ova.ml +++ b/v2v/input_ova.ml @@ -143,18 +143,11 @@ object if Str.string_match rex line 0 then (

I'm trying to write a program that reads an ogg stream and check all the CRC values along the way. But I have big trouble with computing the checksum, or at least I never got checksums that match the one that is in the ogg file. I do set the CRC field in the header to 0 before calculating it. I start with 0 and have no xor at the end. I feed page header with all lacing values and the page

Hello, A little informal input on the TCP/UDP checksum deferral/offload: it fails for me. I have one Xen host, running a snapshot of xen-unstable at 2006-03-24 (9435:11fee62328cc). Each of its domUs are allocated their own /30, with the help of a hacked-up vif script. Prior to working around the problem, Domain-0 could establish TCP connections to other domains. In the case of SSH, it would

On 02/09/2017 12:53 PM, Johnny Hughes wrote: > On 02/09/2017 12:50 PM, Leonard den Ottolander wrote: >> Hello John, >> >> On Thu, 2017-02-09 at 16:33 +0000, John Hodrien wrote: >>> On Thu, 9 Feb 2017, Leonard den Ottolander wrote: >>> >>>> How about my request for checksums in the git repo? >>> >>> What checksums would you

I apologize if this has already been discussed before, but as of yet I have been unable to find any info on the topic. I have a very simple (and common) disk based backup system using rsync, hard links, and a little bit of perl to glue it together. Remote machines are backed up regularly using hardlinks across each snapshot to reduce disk usage. Recently I learned that rsync does a

On 02/09/2017 01:11 PM, Leonard den Ottolander wrote: > On Thu, 2017-02-09 at 12:58 -0600, Johnny Hughes wrote: >> At the time of extraction, the <name>.metadata file is created (again, >> not by us, but by the Red Hat team that distributes source), and all the >> non-text sha1sums are in there as well as all the text sources. > > Aha, <name>.metadata, well,

Folks While trying to automate a download of the ISO files, I ran into inconsistencies with the method of checksums. I was trying to use the checksum values to validate my download. At least in one mirror (mirrors.sonic.net): Centos 7 uses a file called sha256sum.txt containing: 087a5743dc6fd6706d9b961b8147423ddc029451b938364c760d75440eb7be14 CentOS-7-x86_64-DVD-2003.iso

Hello John, On Thu, 2017-02-09 at 16:33 +0000, John Hodrien wrote: > On Thu, 9 Feb 2017, Leonard den Ottolander wrote: > > > How about my request for checksums in the git repo? > > What checksums would you actually want in git? SRPMS are signed which allows the integrity of the contents to be checked. Such an integrity check is missing from the git repo. Either a checksum

On 02/09/2017 12:50 PM, Leonard den Ottolander wrote: > Hello John, > > On Thu, 2017-02-09 at 16:33 +0000, John Hodrien wrote: >> On Thu, 9 Feb 2017, Leonard den Ottolander wrote: >> >>> How about my request for checksums in the git repo? >> >> What checksums would you actually want in git? > > SRPMS are signed which allows the integrity of the

Hello, I have a weird issue with rsync randomly marking some files as having a different checksum (see sample outputs below - run one after another). You would think it is some kind of corruption / io problem with the files but it doesn't seem so - I have copied files around, changes source to different machines, counted md5s manually 100s of times - always the same. All files except

Hi everyone! I played around with rsync sources a little and wrote a small patch that computes the checksums from parts of the files only. I'm just writing to ask if the rsync developers would have any interest in the sort of functionality described below. If you do, I'm willing to work with you to produce a cleaned up patch for git. For background: This started as a way to satisfy an

On Thu, 2017-02-09 at 12:58 -0600, Johnny Hughes wrote: > At the time of extraction, the <name>.metadata file is created (again, > not by us, but by the Red Hat team that distributes source), and all the > non-text sha1sums are in there as well as all the text sources. Aha, <name>.metadata, well, for f.e. bc I see only a checksum for the tarball, but not for the patch files.

Dear all, I report the same problem again, as one of our sysadmins at the university ran into the same issue again. Every so often they find an in-place update of an R package which almost always amounts to a small change in the DESCRIPTION file. This does cause the checksums to change, and we end up with two packages with the exact same version number but different checksums. To date there

I have just seen this, that I thought was an old problem, show up again.. I noticed it when I let a domU stay on DHCP long enough to try to do a renew, then the DHCP server started logging about checksum errors: dhcpd: 5 bad udp checksums in 5 packets DHCP server is 1:9.6.ESV.R4+dfsg-0+lenny1 so newer DHCP releases may contain workaorunds allowing these packets.. Since I had this problem years

Since people are now talking about the SSLv3 security hole and how to disable it, here's a thread where you can talk about that. In Dovecot v2.1+ you can disable SSLv3 by setting: ssl_protocols = !SSLv2 !SSLv3 In older versions you'd have to patch the source code. Attached a patch against v2.0. I don't know if there are any clients that would break by disabling SSLv3. I'd

On Mon, Feb 27, 2023 at 6:41?PM Richard W.M. Jones <rjones at redhat.com> wrote: > > On Mon, Feb 27, 2023 at 04:24:33PM +0200, Nir Soffer wrote: > > On Mon, Feb 27, 2023 at 3:56?PM Richard W.M. Jones <rjones at redhat.com> wrote: > > > > > > > > > https://github.com/kubevirt/containerized-data-importer/issues/1520 > > > > > > Hi