"DRM and TCP...would not be compatible with the GPL."
wyliecoyoteuk wrote:What you should realise is that the Kernel itself is DRM free.
DRM keys are incompatible with the GPL.
However, drivers can be added to the kernel that allow external DRM mechanisms to function. So theoretically, for example, DRM protected media can be played without breaking the law.
This in itself does not mean that the kernel contains DRM.
The case with TCP and DEP is the same:they are just drivers for external modules that implement the functions.
I doubt that many of the freely distributable distros actually contain any of this code, simply because they would have to license it.
Proprietary Distros such as RedHat or Oracle may well do so.
Looks like Stallman agrees with you.
Can you trust your computer? GNU Project
Torvalds seem to have different idea.
LKML: Linus Torvalds: Flame Linus to a crisp!
Linux founder opens door to DRM - CNET News
Linus Torvalds: "No GPL 3 for Linux"
and unfortunately most seem to agree with Torvalds idea.
Trusted Computing and Linux - 2005 Linux Symposium
OLS: Linux and trusted computing [LWN.net]
Enabling DRM in the kernel? [LWN.net]
A fight against evil or a fight for attention - Linux Journal
How DRM prepared the way for Xen/VMware
Linux and TPM - The H Open Source
"drivers can be added to the kernel that allow DRM mechanisms to function." "This in itself does not mean that the kernel contains DRM."
I guess we have far different views on DRM, as I do not distinguish between software DRM and hardware DRM, as both are but two sides of the same wooden nickle. In XP Pro, software nasties like COPP driver, WM-DRM, etc., interlock with hardware nasties like HDCP, and either enable, support or harden it. Saying that COPP is not part of DRM is like saying that DRM has nothing to do with HDCP. Its like claiming that the 'getaway-driver' of bank robbers has no responsibility for whatever happens within the bank. The word that comes to mind is 'accomplice'. So I'd have to disagree with your assessment:
"What you should realize is that the kernel itself is DRM free."
If said kernel contains anything (call it driver, module, tar ball, or whatever) that supports, enables or hardens hardware DRM, then that is software-based DRM, and the kernel definitely appears infected to me.
Linux Kernel Documentation:: intel_txt.txt - mjmwired
Linux kernel Driver Database: CONFIG_INTEL_TXT
Integrity management in the kernel - LWN.net
There's lots of other citations, but I won't bore you to death.
The point being whatever you want to call these bits & pieces of code (or whatever) they are in the kernel. Secondly, whether you view them as harmless or not, I'd like to find a list of them so I can eradicate them (once I learn how).