BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] CrowdStrike
- Subject: [Discuss] CrowdStrike
- From: markw at mohawksoft.com (markw at mohawksoft.com)
- Date: Wed, 24 Jul 2024 11:48:20 -0400
- In-reply-to: <f4851eaa-4477-4618-b2bf-377c74d200be@borg.org>
- References: <741866934157f80503afcde12cc9fcef.squirrel@mail.mohawksoft.com> <f4851eaa-4477-4618-b2bf-377c74d200be@borg.org>
> On 7/24/24 08:21, markw at mohawksoft.com wrote:
>> Thoughts:
>> (1) loading pcode into a kernel driver. Are you kidding me?
>
> What is pcode? Pascal?
I'm not sure which flavor of "pcode" which is a portable code, like java
byte-code.
>
>
>> (2) loading pcode (in any environment) without basic sanity checks
>> (checksum, structural verification, etc.) is total incompetence. This is
>> a
>> disaster waiting to happen, even a little bit-rot could create a problem
>> that would be difficult to diagnose and fix.
>
> Almost as if no one sat down, thought it through, and did a careful
> design. Heck, who needs to think and design anything these days now that
> we have "design patterns" and "best practices"? If the well formatted
> little code changes that reviewers recognize ("design patterns") and
> don't need to think about get approved, that's "best practices"!
I know, it's insane.
>
>
>> (3) Unstaged rollout: amateur hour nonsense.
>
> That is something they were explicitly selling as a feature (speed!),
> not a bug. Right?
>
Seriously.
>
> -kb
>
> _______________________________________________
> Discuss mailing list
> Discuss at driftwood.blu.org
> https://driftwood.blu.org/mailman/listinfo/discuss
>
- References:
- [Discuss] CrowdStrike
- From: markw at mohawksoft.com (markw at mohawksoft.com)
- [Discuss] CrowdStrike
- From: kentborg at borg.org (Kent Borg)
- [Discuss] CrowdStrike
- Prev by Date: [Discuss] CrowdStrike
- Next by Date: [Discuss] CrowdStrike
- Previous by thread: [Discuss] CrowdStrike
- Next by thread: [Discuss] CrowdStrike
- Index(es):
