this post was submitted on 22 Jul 2023
2614 points (99.2% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
56516 readers
453 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):
🏴☠️ Other communities
Torrenting:
Gaming:
💰 Please help cover server costs.
![]() |
![]() |
---|---|
Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Question: Firefox renders certain DRM content in containers. Would that be applicable here? (Run unmodified site in container in background, load site content from that to user, and direct the attestor to the container so that the user can modify the site on the front end)?
The point of this is so that the user can't modify the site at all, despite what the proposal might say. Their goals and non-goals are contradictory.
Running this content in a container will not protect you. Just don't even try to adapt to it. Reject it completely.
What I mean is, if the attestor checks the integrity of the site, why couldn’t the unmodified site be ran in a container to trick the attestor?
Possibly, but it sounds like a pain to work with, if I understand the technical details correctly.