[Not really OT] Crowdstrike Analysis: It was a NULL pointer from the memory unsafe C++ language.

Paolo Invernizzi paolo.invernizzi at gmail.com
Wed Jul 24 11:31:20 UTC 2024


On Wednesday, 24 July 2024 at 07:31:21 UTC, Kagamin wrote:
> On Tuesday, 23 July 2024 at 09:28:07 UTC, Paolo Invernizzi 
> wrote:
>> What about sanitise the input while ingesting it?
>
> What it should do after sanitization? Resume? In misconfigured 
> state?

As it seems that the kernel module that's ingesting the 
configuration files is marked as required for boot, that module 
should just raise an hand signalling "Huston, we have a problem" 
to the management console, and do nothing at all.

/P




More information about the Digitalmars-d mailing list