Originally posted by chilinux
View Post
Thus the only possible use I would have for this (thus only reason to include it in my kernel builds) would be if I were repurposing the code to do something with my own keys such as some form of encrypted video chat (video other than public) with no easy way for malware to screenshot and export private content. Screenshots would work when I want them to, not when an enemy trying to break into my system wants them to. This of course is of value only if exporting screenshots is significantly easier than remotely installing keyloggers and camera bugs.
From Hollywood's viewpoint, it's easier to crack HDCP than it is to root movie studio computers or steal physical copies from vaults. For dissidents or porn affectionados having a private video chat, this may not work out quite the same. Posession is root, and a computer, phone, or tablet left in an empty hotel room is vulnerable to all sorts of well known attacks, notably hardware keylogger installation in a laptop. Most of the folks using the chat would have better things to do than surf tech sites to keep up with the latest threats and patch on a daily basis, while movie studios can afford to pay people to do exactly that. Hell, they still get cracked, so for the general public matters are even worse.
The other problem of course is that it may not be possible to re-use HDCP's hardware support or any other hardware DRM setup (PSP I'm looking at you) with keys that can themselves be trusted for this sort of thing. I know we have things like Signal being able to turn off screenshots by default on Android, but I don't know if that's just telling normal screenshot programs not to run, marking some RAM as private(possibly reusing something written for DRM purposes?), or something more robust.
Comment