1. 45
  1.  

  2. 8

    Was it evil of me that I checked to see if their hex dump had also been sanitized to redact the paths redacted in the text part of “TCP Payload Corruption”?

    1. 6

      The thing that jumped out at me was, “How is their environment so heterogeneous?” Multiple kernel versions with multiple versions of Xen with Xen in different modes, I’m surprised they found it.

      1. 2

        This might seem odd, however its not unusual. A couple of the reasons that come to mind

        • early discovery of problems, eg. production is run on version 2.x, testing environments run on 2.x and 3.x. This way problems that may be present on newer versions can be detected early.
        • segmentation might minimize the effects of a bug into only a subset of systems.
        • diversify your environment eg. tor-bsd diversity project.

        Not necessarily valid reasons for the case at hand, but just to give some ideas.

        1. 1

          I noticed that too, often the version of Xen is out of your control if you’re running on top of IaaS, but the Linux version? I am very curious as to why you would run that many different kernels.

          1. 1

            This is speculation, but I wonder if that helps in some ways. Once you’ve found an environment where it happens, and one where it doesn’t, you can narrow your search to the differences between the two.

          2. 3

            This is a seriously deep rabbit hole. Kudos to not only finding all these bugs but having the patience to write them up.