Technology

59651 readers

2643 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

Microsoft points finger at the EU for not being able to lock down Windows (www.neowin.net)

submitted 4 months ago by neme@lemm.ee to c/technology@lemmy.world

90 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] kureta@lemmy.ml 0 points 4 months ago (1 children)

But in this case Microsoft certified the driver. If they knew the driver included an interpreter that can run arbitrary code, they shouldn't have certified it because they can not fully test it. If they didn't know, then their certification test are inadequate. Most of the blame lies with the security software. If Microsoft didn't certify it, they would have had zero fault.

[–] conciselyverbose@sh.itjust.works 0 points 4 months ago (2 children)

Certifying a driver is not an endorsement.

It is a verification that it is legitimately from who it claims to be from. Microsoft has zero fault, period.

[–] umami_wasbi@lemmy.ml 0 points 4 months ago (1 children)

I had a read about the WHQL (which I assumes what certified means). It uses the Windows HLK to perform a series of tests, which submited to Microsoft, and only then the driver will be signed.

While certification isn't endorsement, the testing and the resulting certification implies basic compatibility and reliability. And causing bootloops and BSODs is anywhere but close to "basic compatibility and reliability."

[–] punkfungus@sh.itjust.works 0 points 4 months ago (1 children)

Crowdstrike bypassed WHQL because the update was not to the driver, it was to a configuration file that then gets ingested by the driver. It's deliberate so they can push out updates for developing threats without being slowed down by the WHQL process.

And that means when they decide to just send it on a Friday with a buggy config file, nobody is responsible but Crowdstrike.

[–] umami_wasbi@lemmy.ml 0 points 4 months ago* (last edited 4 months ago)

Oh wow. Then definitely CS is in fault. What a brilliant idea they have.

[–] kureta@lemmy.ml 0 points 4 months ago (1 children)

The Windows Hardware Certification program (formerly Windows Hardware Quality Labs Testing, WHQL Testing, or Windows Logo Testing) is Microsoft's testing process which involves running a series of tests on third-party device drivers, and then submitting the log files from these tests to Microsoft for review. The procedure may also include Microsoft running their own tests on a wide range of equipment, such as different hardware and different Microsoft Windows editions.

[–] sandalbucket@lemmy.world 0 points 4 months ago* (last edited 4 months ago)

For the Nth time, crowdstrike circumvented the testing process

Edit: this is not to say that cs didn’t have to in order to provide their services, nor is this to say that ms didn’t know about the circumvention and/or delegate testing of config files to CS. I’ll take any opportunity to rag on MS, but in this case it is entirely on CS.