this post was submitted on 22 Jul 2023
2608 points (99.2% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

54746 readers
222 users here now

⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.

Rules • Full Version

1. Posts must be related to the discussion of digital piracy

2. Don't request invites, trade, sell, or self-promote

3. Don't request or link to specific pirated titles, including DMs

4. Don't submit low-quality posts, be entitled, or harass others



Loot, Pillage, & Plunder

📜 c/Piracy Wiki (Community Edition):


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 1 year ago
MODERATORS
 

looks like rendering adblockers extensions obsolete with manifest-v3 was not enough so now they try to implement DRM into the browser giving the ability to any website to refuse traffic to you if you don't run a complaint browser ( cough...firefox )

here is an article in hacker news since i'm sure they can explain this to you better than i.

and also some github docs

you are viewing a single comment's thread
view the rest of the comments
[–] argv_minus_one@beehaw.org 0 points 1 year ago (1 children)

Criminals will crack the DRM in short order—they always do—so that idea won't last long.

And no, the DRM can't be updated to fix the vulnerability if it's implemented in firmware. Not without shutting out absolutely everyone whose computer/phone is more than 3 years old, and there's not a snowball's chance in hell that banks will do that when half of their customers are old farts with decade-old computers and an “if it ain't broke, don't fix it” attitude.

[–] frog@programming.dev 2 points 1 year ago (1 children)

Wait were they seriously looking to implement it at a FIRMWARE level? jesus that's just stupid.

[–] argv_minus_one@beehaw.org 2 points 1 year ago (1 children)

If they implement it in hardware, then fixing vulnerabilities is completely impossible instead of only mostly impossible.

[–] frog@programming.dev 2 points 1 year ago (1 children)

I was just expecting it to be something built into chrome, similar to how drivers need to be signed to run in windows, they'd force you to use browsers Signed By Google to be verifiably compliant with the DRM. It seems like the easiest option for them and the most well understood since it's been used for drivers for so long

[–] argv_minus_one@beehaw.org 1 points 1 year ago* (last edited 1 year ago)

If they implement it in pure software, then it's easy to crack.

They're not going to wrap Chrome in Denuvo because that would ruin its performance. The last thing they want is for Firefox to be not only faster but dramatically faster. Performance is a big part of how Internet Explorer lost its market share. And even if they do wrap it in Denuvo, Empress will no doubt show them the error of their ways.

So yes, I expect they will use firmware/hardware, presumably TPM or Microsoft Pluton, to implement this.