This is different, and doesn’t address screen recording.
HDCP uses three systems:[5]
Authentication prevents non-licensed devices from receiving content.
Encryption of the data sent over DisplayPort, DVI, HDMI, GVIF, or UDI interfaces prevents eavesdropping of information and man-in-the-middle attacks.
Key revocation prevents devices that have been compromised and cloned from receiving data.
It would stop someone from playing DRM content to an unauthorized TV, but does not mention anything about screen recording your own device. There are some built in protections for preventing an application from being recorded but I have no doubt there are bypasses
Maybe I’m not following but this seems to be talking about applications communicating with hardware designed to be authorized to play.
How would a video playing on a browser like YouTube on my existing, old hardware be able to parse what’s authorized? Short of making YouTube a program on my computer, how does it on a browser know what else I’m running?
Yes: https://en.wikipedia.org/wiki/High-bandwidth_Digital_Content_Protection
This is different, and doesn’t address screen recording.
It would stop someone from playing DRM content to an unauthorized TV, but does not mention anything about screen recording your own device. There are some built in protections for preventing an application from being recorded but I have no doubt there are bypasses
Maybe I’m not following but this seems to be talking about applications communicating with hardware designed to be authorized to play.
How would a video playing on a browser like YouTube on my existing, old hardware be able to parse what’s authorized? Short of making YouTube a program on my computer, how does it on a browser know what else I’m running?