Shrinking shrinker locking overhead
Shrinking shrinker locking overhead
Posted Sep 16, 2023 4:50 UTC (Sat) by NYKevin (subscriber, #129325)In reply to: Shrinking shrinker locking overhead by pizza
Parent article: Shrinking shrinker locking overhead
> (3) As used in this subsection—
> (A) to “circumvent a technological measure” means to descramble a scrambled work, to decrypt an encrypted work, or otherwise to avoid, bypass, remove, deactivate, or impair a technological measure, without the authority of the copyright owner; and
> (B) a technological measure “effectively controls access to a work” if the measure, in the ordinary course of its operation, requires the application of information, or a process or a treatment, with the authority of the copyright owner, to gain access to the work.
If you don't meet the test in (B), then it's not DRM and there's no 1202 liability. You don't need "the authority of the [kernel's] copyright owner" to mark your own module as GPL'd (and thereby gain access to GPL-only interfaces), so the GPL-only restriction does not effectively control access to the kernel within the meaning of 1202.
1203 is more debatable:
> (a) False Copyright Management Information.—No person shall knowingly and with the intent to induce, enable, facilitate, or conceal infringement—
> (1) provide copyright management information that is false, or
> [...]
> (c) Definition.—As used in this section, the term “copyright management information” means any of the following information [...], except that such term does not include any personally identifying information about a user [...]:
> [...]
> (6) Terms and conditions for use of the work.
So you could argue that, by falsely marking your module as GPL'd, you're violating this law. OTOH, one could make exactly the same argument about the upstream GPL-only marker, as derivative works don't really follow bright line rules like that in the first place. I suspect a US court would at least seriously consider applying the equitable doctrine of unclean hands in such a scenario (i.e. you cannot violate the law, and then sue somebody else for violating the law, when your violation directly caused their violation).
However, there is a far more straightforward defense: If you didn't have "the intent to induce, enable, facilitate, or conceal infringement" (because you honestly believe that your module is not a derivative work), then you don't violate (a) and therefore haven't broken the law at all.
