Live data from Hacker News

TPP banning requirements to transfer or access to source code of software

keionline.org

101–110 of 162 posts

Re: TPP banning requirements to transfer or access to source code of software

#101
post #95

Earlier quoted context omitted.

Why would the GPL not be considered a commercially negotiated contract?

If the TPP is ratified, would it be worth updating the GPL to say "You agree that this is a commercially negotiated contract"?

The FSF says that GPL is not a contract [1] [2] [3].

[1] http://www.gnu.org/licenses/200104_seminar.html

[2] http://www.gnu.org/philosophy/enforcing-gpl.html

[3] https://www.fsf.org/news/wallace-vs-fsf

Re: TPP banning requirements to transfer or access to source code of software

#102

"Party" here means party to the treaty, right? So, governments can't require source disclosure (except for critical infrastructure), but this specifically exempts contracts about such from this rule: > [Nothing in this Article shall preclude] the inclusion or implementation of terms and conditions related to the provision of source code in commercially negotiated contracts It seems like this wouldn't affect licensing…

It prevents the government from saying "You can't sell your software in our country unless we can see the code."

And that's about it.

Re: TPP banning requirements to transfer or access to source code of software

#103
post #4

These are rules for States. It has no bearing whatsoever on the GPL. This prevents a country from forcing somebody like Microsoft or Apple to give up their source code for "inspection" in order to access their market. It also helps to prevent States from demanding and acquiring encryption or other private keys (there's a separate section that also explicitly forbids mandating backdoors be added). Not everything in th…

"These are rules for States. It has no bearing whatsoever on the GPL."

TPP is designed to give commercial entities equivalent rights to nation states. That's what the 'Investor-State Dispute Settlement' provisions refer to. Under these provisions a commercial entity could 'steal' Open Source code, without the requirement to release the source code. In effect rendering licenses such as the GPL unenforceable. At the very least it may cause a dilution and hinder the growth of the Open Source sector. Now I wonder whose interests that that would advance and who helped to write such provisions.

Re: TPP banning requirements to transfer or access to source code of software

#104
post #34
post #5

Would this prevent us from requiring VW make available it's source code? Not a lawyer.

Why would you want VW to make available its source code?

To audit the firmware of the emission control systems in their cars, for example.

Re: TPP banning requirements to transfer or access to source code of software

#105
post #7

The "parties" of a treaty are governments. This has nothing to do with GPL. This is saying that a government can't say "you aren't allowed to sell software in the country of Frain as a non-Frainian unless you provide the source code for that product (whether to the end user or to the government)". They leave an exception for "critical infrastructure", because it was hard to argue that the government of Frain shouldn'…

> ...mostly about forcing capitalism on nation states..

And these non-capitalist countries are?

All countries are capitalist. They may claim otherwise, but if the party that paid for the means of production makes a claim on the value of the produced goods, then they are capitalist. It doesn't matter if the party that provided the capital was a private citizens or a government. If the workers that produced the goods don't have sole claim on the value of what they produced, the system is capitalist. The only difference in the USSR, Maoist China or even North Korea is that the state tried to monopolize capital.

Re: TPP banning requirements to transfer or access to source code of software

#106
post #4

These are rules for States. It has no bearing whatsoever on the GPL. This prevents a country from forcing somebody like Microsoft or Apple to give up their source code for "inspection" in order to access their market. It also helps to prevent States from demanding and acquiring encryption or other private keys (there's a separate section that also explicitly forbids mandating backdoors be added). Not everything in th…

So, as an actual lawyer i actually think i disagree with you in practice. Imagine for a second that the US gets tough on GPL violators, and says "well, if you want to sell android devices in the US, you have to produce the GPL source code". Or something even simpler, along the lines of "products marketed in the US must comply with all licensing obligations of software that it contains". This one actually happens behi…

It's worth pointing out that legal language almost always permits more than one interpretation, which is why disputes are adjudicated by humans in (hopefully) impartial courts, under processes that permit the parties to provide testimony and evidence to support one or the other interpretation.

So, just because a piece of legal language can be interpretted a certain way, that does not mean it is likely to prevail in court. In this sort of case, I'd be surprised if any TPP negotiator or representative, or any documentation from the TPP process, will indicate that this language was intended to break the GPL and open source in general.

Re: TPP banning requirements to transfer or access to source code of software

#107
post #15

Earlier quoted context omitted.

It also would prevent government agencies from demanding i.e. the source code of a car's ECU to verify its safety and emissions behavior. The only way out of this would be to declare car ECUs (or other systems) as "critical infrastructure", the definition of which I'm sure will be subject to many political tug-of-wars once this is implemented.

Playing the devil's advocate here, but you shouldn't need access to a car's source code to measure its emissions. The test is broken, not the software.

The test should be to validate software is correct.

Re: TPP banning requirements to transfer or access to source code of software

#108
post #4

These are rules for States. It has no bearing whatsoever on the GPL. This prevents a country from forcing somebody like Microsoft or Apple to give up their source code for "inspection" in order to access their market. It also helps to prevent States from demanding and acquiring encryption or other private keys (there's a separate section that also explicitly forbids mandating backdoors be added). Not everything in th…

"These are rules for States. It has no bearing whatsoever on the GPL." TPP is designed to give commercial entities equivalent rights to nation states. That's what the 'Investor-State Dispute Settlement' provisions refer to. Under these provisions a commercial entity could 'steal' Open Source code, without the requirement to release the source code. In effect rendering licenses such as the GPL unenforceable. At the ve…

That is not what investor-state dispute resolution does. If it was, the GPL would have been broken a long time ago because ISDS has been part of bilateral treaties for decades.

ISDS is intended to provide standing for a company from one country to request relief from the government of another country. Without ISDS, the Vietnamese national government could simply take whatever U.S. property is located in Vietnam, and the U.S. company would have no recourse.

Re: TPP banning requirements to transfer or access to source code of software

#109
post #4

These are rules for States. It has no bearing whatsoever on the GPL. This prevents a country from forcing somebody like Microsoft or Apple to give up their source code for "inspection" in order to access their market. It also helps to prevent States from demanding and acquiring encryption or other private keys (there's a separate section that also explicitly forbids mandating backdoors be added). Not everything in th…

Just to agree with this point and elaborate: when the text uses the word "party" it refers to a nation signing the treaty, and not people. So when it says "No Party shall require the transfer of, or access to, source code of software owned by a person of another Party, as a condition for the import, distribution, sale or use of such software, or of products containing such software, in its territory," Party refers to…

In a State where the GPL is enforceable would it be a violation of the TPP to require that a foreign company comply with the GPL and release the source code? I think that's the $1,000,000 question.

Re: TPP banning requirements to transfer or access to source code of software

#110
An interesting side effect of this would be the invalidation of the Nevada law requiring the source code for all electronic gambling machines be disclosed in order to operate in that state.

It seems like it would also apply to new or existing laws requiring the disclosure of code inside proprietary voting machines, medical equipment, and of course, the Volkswagon ECU. Then again, could those things be considered "critical infrastructure"?

The Department of Homeland Security considers the entire "Information Technology sector" as "critical infrastructure":

http://www.dhs.gov/information-technology-sector

Post reply on HN