![](https://lemm.ee/api/v3/image_proxy?url=https%3A%2F%2Fawful.systems%2Fpictrs%2Fimage%2F37a70490-5957-4b8d-a439-20cd212109fc.png)
![](https://lemm.ee/api/v3/image_proxy?url=https%3A%2F%2Fawful.systems%2Fpictrs%2Fimage%2F8651f454-1f76-42f4-bb27-4c64b332f07a.png)
https://www.crowdstrike.com/blog/technical-details-on-todays-outage/
This is not related to null bytes contained within Channel File 291 or any other Channel File.
That to me implied that the channel file wasn’t actually necessarily corrupt (or as corrupt as people thought), but that it triggered a logic error. In particular this point implies that it wasn’t from garbage zero bytes in the file.
(That said I could have worded this better, in my defense I’m sick in bed and only half thinking straight)
The prompt lol: