3 ms·

I am not defending of excusing anything. I am saying there is not enough information to make a judgement one way or the other. Right now, we have almost zero te

by arp242 2y ago

I am not defending of excusing anything. I am saying there is not enough information to make a judgement one way or the other. Right now, we have almost zero technical details. Call me old-fashioned and boring, but I'd like to have some basic facts about the situation first. After this I decide who does and doesn't deserve a bollocking.

chrisjj 2y ago
I think we do have enough info to judge e.g. :This should not have passed a competent C/I pipeline for a system in the critical path." Thay info includes that the faulty file consisted entirely of zeros.
- arp242 2y ago
  > That info includes that the faulty file consisted entirely of zeros. Even that is not certain. Some people are reporting that this isn't the case and that the all-zeroed file may be a "quick hack" to send out a no-op. So no, we have very little info.
  - chrisjj 2y ago
    But the all-zero file is version CS has IDed as the cause, right?
    - zmatt 2y ago
      No, CS has explicitly stated that the cause was a logic error in the rules file. They have also stated "This is not related to null bytes contained within Channel File 291 or any other Channel File."
- deleted 2y ago
  [deleted]