Suits and Patents: A Report from the GPLv3 Launch Conference
Posted Jan 23, 2006 18:59 UTC (Mon) by kirkengaard
Parent article: Suits and Patents: A Report from the GPLv3 Launch Conference
Not having been there, it sounds like a very good summary of a very good meeting. It's nice to have this virtuality about what is going on where.
" ... but a question was also asked about the definition of "Complete Corresponding Source Code" in Section 1 where it includes "any encryption or authorization codes necessary to install and/or execute the source code". The specific concern was about whether code could be encrypted with GnuPG for sending, but I failed to understand the issue as to my mind you would be encrypting it with the recipient's key, so they would already have it."
I also see the question as mistaken; "any encryption or authorization codes necessary to install and/or execute the source code" tends more to evoke the possibility of black-box encryption schemes and non-open document or media encoding such that the open source of the program, without the encryption or authorization, is not functional. A Gatesian bargain of sorts, if you will. Opening the source with the exception of the bits that make it functional, allow it to interoperate, or authorize its use. Especially in the coming TPM era. "Sure, have the source. You can't do anything with it, but here you go.", foreclosed by this provision in GPL v3.
to post comments)