linux-kernel - Re: how about mutual compatibility between Linux's GPLv2 and GPLv3?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 Jun 2007 14:52:11 -0300
From:	Alexandre Oliva <oliva@....ic.unicamp.br>
To:	linux-kernel@...r.kernel.org
Subject: Re: how about mutual compatibility between Linux's GPLv2 and GPLv3?

On Jun 28, 2007, Alexandre Oliva <oliva@....ic.unicamp.br> wrote:

> So, let's narrow the scenario to: tivoized machine downloads binary
> from protected site, refrains from downloading sources that it could
> download, user can still access and copy the binaries, but can't
> obtain the sources because the machine opted not to get them.

> Now, the user can't distribute the binaries, because doing so without
> being able to get the sources to pass them on would be copyright
> infringement.  Would a court see this as a restriction on distribution
> imposed by the distributor?  Or by the copyright holder?

I'm not sure my point was clear (not even to myself), so let me try to
clarify with a slightly different scenario.

Software vendor places Free Software program for sale on a web site.
Customers pay a fee and are granted access to a web page from which
they can download both binaries and sources.  The web page encourages
them to download the sources first, because, one hour after the
download of the binary completes, the password that grants access to
the web page and to the downloadable bits is revoked.

Sloppy customer downloads only the binaries.  Days later, they decide
they want to hire someone else to modify the software for them.  Then
they realize they don't have the sources, and that they declined the
opportunity to have them.  So they can't reasonably modify the
software, or distribute the software for another party to do it for
them.  They got themselves into this situation by declining the source
download.  The software distributor is not imposing a restriction,
it's the copyright holder that is, through the license.

Now, compare this with the case quoted above, in which the computer,
on behalf of the customer, declines the source download.  Clearly the
license stops the user from distributing the software in these
circumstances, and practical matters pretty much stop the user from
modifying the software for any other purpose, but how is this
different from the unquoted case above?  Can one actually claim that
the tivoizing vendor is imposing a further restriction, even though
the restrictions actually stems from a decision made by the user (or
rather by the computer acting on the user's behalf), and from the
copyright holder?  How could this be phrased as a further restriction,
if the license already restricts distribution without source code, and
concedes that not having the source code makes it nearly impossible to
make modifications?

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@...d.ic.unicamp.br, gnu.org}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/