loopholes
Posted Apr 7, 2006 17:50 UTC (Fri) by
stevenj (guest, #421)
In reply to:
Bruce Perens: State of Open Source by dlang
Parent article:
Bruce Perens: State of Open Source
for the other poster above who said that in my example redhat wouldn't have
my box as the 'primary inteneded use' of the software so it wouldn't apply, if that's all it
takes it's pretty easy for a company to have an official 'primary intended use' for something
that doesn't involve a locked down box, but that also gets used on a locked down box and
at least argue plausably that they are not violating things.
I didn't say "primary intended use". I used the words in the (draft) GPLv3:
"recommended or principal context of use". And so should you.
Your claim is not very plausible. If you ship a locked-down box bundled with
GPL-derived software that has been modified to add DRM, then it seems very hard to argue
with a straight face that you are not "recommending" that users employ the software you
give them with the hardware you sell them.
Yes, you could try to imagine a hypothetical DRM hardware maker who doesn't include
software with their device, but rather requires you to download it from some third party who
has nothing
to do with DRM, but that is quite a stretch. First, forcing hardware manufacturers to not
bundle the software customers need to use the hardware is imposing quite a penalty on
them. Second, it seems unlikely that if you want to enforce DRM you're going to rely on the
cooperation of a third party who has no financial interest in enforcing DRM on your
hardware.
By all means, bring this up with the GPLv3 committees (and for the same reason, it's
probably not worth arguing more about it here). However, I'm inclined to give some
credence to the ability of a law professor who has spent years enforcing the GPL, and
thereby inclined to doubt any random fellow who claims there are "obviously" huge
loopholes.
(
Log in to post comments)