this post was submitted on 22 Jul 2023
2303 points (98.9% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54443 readers
1128 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 |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Wait were they seriously looking to implement it at a FIRMWARE level? jesus that's just stupid.
If they implement it in hardware, then fixing vulnerabilities is completely impossible instead of only mostly impossible.
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
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.