What does "supports DRM and may not be fully accessible" mean for SATA SDDs?

Original Article ↗ Hacker News Discussion ↗

Technical meaning of “supports DRM and may not be fully accessible”

  • Message is triggered for SATA devices that support ATA Trusted Send/Receive commands and TCG-style on-disk encryption features.
  • Linux libata gates some of these commands behind libata.allow_tpm=1; “TPM” there is an unfortunate acronym clash and unrelated to the platform TPM chip.
  • One view: in this specific case it’s about self‑encrypting drive features, not consumer media DRM.
  • Counterpoint: kernel comments reference DVR use and CPRM (Content Protection for Recordable Media), explicitly a DRM scheme; some paths clearly are about copy‑protection.
  • For the SSD in the original question, the warning likely comes from a non-compact-flash code path, so exact linkage to CPRM remains unclear.

DRM, control, and security

  • Many see these mechanisms as part of a broader trend: hardware + services collaborating to lock users out, especially of custom OS builds, rooted phones, or non‑certified PCs.
  • Repeated claim: the same tech used for “security” is also used to treat the owner as the threat actor; DRM and cybersecurity share tools, differing mainly in whose interests are protected.
  • Others argue the tech can be beneficial when user‑controlled (e.g., self‑encrypting drives, HSMs, secure PIN checks) but becomes abusive when vendors hold the keys.
  • Some take a hard line that any tech enabling remote control over owner devices is inherently harmful and should be banned.

Markets, capitalism, and regulation

  • One camp believes “vote with your wallet” should solve DRM; if people dislike it, they won’t buy.
  • Many rebut this: alternatives often don’t exist, industry self‑regulation and certification (e.g., Microsoft PC certification, HDMI/HDCP licensing) create de facto monopolies.
  • Several argue current DRM reality is capitalism functioning: maximizing control and extractable revenue, not user freedom, hence the need for regulation.
  • File sharing and DRM‑free purchases are discussed as counter‑pressures, but seen as niche compared to mainstream, locked‑down content.

Practical impacts and future concerns

  • Examples of real‑world pain: HDCP blocking presentations, codec hassles, HDMI licensing barriers for open‑source drivers, SD cards bound to devices.
  • Fears that banking, media, and other apps will increasingly require attested, non‑modifiable systems, pushing general‑purpose computing toward locked appliances.
  • Some accept stricter environments for fraud reduction; others see this as unacceptable erosion of owner control.