Comment KW4Z Re: Where did the comments go?

Story

Grsecurity stops issuing public patches, citing trademark abuse

Preview

Where did the comments go? (Score: 0)

by Anonymous Coward on 2015-09-09 04:08 (#KVWG)

>BTW: show me the part in the GPL that states that you must make the source code available to anyone?

Please keep up. Read the above posts.

Short story: If the GPLv2 is a license then we simply revoke spenglers permission to modify the linux source code. There's no 'no-revocation' clause. This is why the GPLv3 had to be drafted. Licenses arise from property law, read up on them. They are not a product of copyright law as all lay techies suppose.

If you argue the GPLv2 is a contract, then, as you may note, the GPLv2 is not a fully integrated document (notice there's no integration clause?), then extrinsic evidence comes in to show that the rightsholders never intended source code of derivative works to be closed in this manner. Usage in trade and course of dealings of the party come in.

If it matters, this case is distinguishable from RedHat etc as RedHat is simply failing to distribute binaries to anyone not contracting with them, whereas it does publish source code (and for a reason). Here Spengler wills to close the source code to a derivative work.
And: if it matters: RedHat's approach has not been tested in court.

You probably don't get to argue contract, as has been stated earlier, so a plaintiff just revokes the license and you're done with grsecurity: you want to close it, it will be closed, completely.

You ever wonder why the FSF requires all copyrights to be assigned to them in their projects. Any one of the 10's of 1000s of linux contributors can be a plaintiff, they all have standing.

Re: Where did the comments go? (Score: 2, Informative)

by evilviper@pipedot.org on 2015-09-09 06:11 (#KW4Z)

Spengler announced he is closing grsecurity
No he isn't doing that at all. The summary states this fact quite clearly.
it's ok to distribute copies of his work for a fee, as long as the source code is published isn't it? He is not publishing the source code. He is keeping it closed, except to people who pay
The GPLv2 has NEVER required source code be "published". It only requires that any recipient of "object code" also be able to receive the source code, and you "may not impose any further restrictions on the recipients" meaning they could redistribute it further.

This is in the FAQ for anyone who spent a few seconds to look for it:
* http://www.gnu.org/licenses/gpl-faq.html

"the GPL requires you to make the modified source code available to the program's users, under the GPL."

"The GPL gives him permission to make and redistribute copies of the program if and when he chooses to do so. He also has the right not to redistribute the program, when that is what he chooses."

"You can charge people a fee to get a copy from you. You can't require people to pay you when they get a copy from someone else."

etc. etc.
licenses can be revoked at any time by the rights holder
The GPL is not revocable:
* http://www.groklaw.net/article.php?story=2006062204552163
* http://www.gnu.org/licenses/gpl-faq.html#CanDeveloperThirdParty
There's no 'no-revocation' clause. This is why the GPLv3 had to be drafted.
US law doesn't allow revocation, unless explicitly specified in license, which the GPLv2 does NOT. See sources above.

The FSF explained why they needed GPLv3 (patent deals, Tivoization, DRM, etc.), and NOWHERE did they list revocation as being an issue:
* https://www.gnu.org/licenses/rms-why-gplv3.html
You ever wonder why the FSF requires all copyrights to be assigned to them in their projects.
No, because they've explained why... "successful enforcement depends on having the cooperation of all authors."
* https://www.gnu.org/licenses/why-assign.html
the rights holders never intended that someone may close a derivative work
Your repeated assertions of bad faith are both incredibly lazy and utterly insane, as the GPLv2 explicitly allows modifications & derivatives, explicitly allows you to "charge a fee", and nowhere claims you must make your modified version PUBLICLY AVAILABLE. Stop pretending to be a lawyer who has any clue what he is talking about, when you're clearly unwilling to do the slightest work to investigate the validity of your own unsupported claims. I won't be bothering, again.

At least you managed to avoid blaming Debian or women for any of this...

History


Deprecated: mb_convert_encoding(): Handling HTML entities via mbstring is deprecated; use htmlspecialchars, htmlentities, or mb_encode_numericentity/mb_decode_numericentity instead in /var/pipedot/include/diff.php on line 25

Deprecated: Creation of dynamic property FineDiff::$granularityStack is deprecated in /var/pipedot/lib/finediff/finediff.php on line 217

Deprecated: Creation of dynamic property FineDiff::$edits is deprecated in /var/pipedot/lib/finediff/finediff.php on line 218

Deprecated: Creation of dynamic property FineDiff::$from_text is deprecated in /var/pipedot/lib/finediff/finediff.php on line 219

Deprecated: Creation of dynamic property FineDiff::$last_edit is deprecated in /var/pipedot/lib/finediff/finediff.php on line 372

Deprecated: Creation of dynamic property FineDiff::$stackpointer is deprecated in /var/pipedot/lib/finediff/finediff.php on line 373

Deprecated: Creation of dynamic property FineDiff::$from_offset is deprecated in /var/pipedot/lib/finediff/finediff.php on line 375

Deprecated: Creation of dynamic property FineDiffReplaceOp::$fromLen is deprecated in /var/pipedot/lib/finediff/finediff.php on line 126

Deprecated: Creation of dynamic property FineDiffReplaceOp::$text is deprecated in /var/pipedot/lib/finediff/finediff.php on line 127

Deprecated: Creation of dynamic property FineDiffCopyOp::$len is deprecated in /var/pipedot/lib/finediff/finediff.php on line 155

Deprecated: Creation of dynamic property FineDiffCopyOp::$len is deprecated in /var/pipedot/lib/finediff/finediff.php on line 155

Deprecated: Creation of dynamic property FineDiffReplaceOp::$fromLen is deprecated in /var/pipedot/lib/finediff/finediff.php on line 126

Deprecated: Creation of dynamic property FineDiffReplaceOp::$text is deprecated in /var/pipedot/lib/finediff/finediff.php on line 127

Deprecated: Creation of dynamic property FineDiffCopyOp::$len is deprecated in /var/pipedot/lib/finediff/finediff.php on line 155

Deprecated: Creation of dynamic property FineDiffReplaceOp::$fromLen is deprecated in /var/pipedot/lib/finediff/finediff.php on line 126

Deprecated: Creation of dynamic property FineDiffReplaceOp::$text is deprecated in /var/pipedot/lib/finediff/finediff.php on line 127

Deprecated: Creation of dynamic property FineDiffCopyOp::$len is deprecated in /var/pipedot/lib/finediff/finediff.php on line 155

Deprecated: Creation of dynamic property FineDiffCopyOp::$len is deprecated in /var/pipedot/lib/finediff/finediff.php on line 155

Deprecated: Creation of dynamic property FineDiffInsertOp::$text is deprecated in /var/pipedot/lib/finediff/finediff.php on line 104
2015-09-09 06:11
Spengler announced he is closing grsecurity
No he isn't doing that at all. The summary states this fact quite clearly.
it's ok to distribute copies of his work for a fee, as long as the source code is published isn't it? He is not publishing the source code. He is keeping it closed, except to people who pay
The GPLv2 has NEVER required source code be "published". It only requires that any recipient of "object code" also be able to receive the source code, and you "may not impose any further restrictions on the recipients" meaning they could redistribute it further.

This is in the FAQ for anyone who spent a few seconds to look for it:
* http://www.gnu.org/licenses/gpl-faq.html

"the GPL requires you to make the modified source code available to the program's users, under the GPL."

"The GPL gives him permission to make and redistribute copies of the program if and when he chooses to do so. He also has the right not to redistribute the program, when that is what he chooses."

"You can charge people a fee to get a copy from you. You can't require people to pay you when they get a copy from someone else."

etc. etc.
licenses can be revoked at any time by the rights holder
The GPL is not revocable:
* http://www.groklaw.net/article.php?story=2006062204552163r>* http://www.gnu.org/licenses/gpl-faq.html#CanDeveloperThirdPartylockquote>There's no 'no-revocation' clause. This is why the GPLv3 had to be drafted.US law doesn't allow revocation, unless explicitly specified in license, which the GPLv2 does NOT. See sources above.

The FSF explained why they needed GPLv3 (patent deals, Tivoization, DRM, etc.), and NOWHERE did they list revocation as being an issue:
* https://www.gnu.org/licenses/rms-why-gplv3.html
You ever wonder why the FSF requires all copyrights to be assigned to them in their projects.
No, because they've explained why... "successful enforcement depends on having the cooperation of all authors."
* https://www.gnu.org/licenses/why-assign.html
the rights holders never intended that someone may close a derivative work
Your repeated assertions of bad faith are both incredibly lazy and utterly insane, as the GPLv2 explicitly allows modifications & derivatives, explicitly allows you to "charge a fee", and nowhere claims you must make your modified version PUBLICLY AVAILABLE. Stop pretending to be a lawyer who has any clue what he is talking about, when you're clearly unwilling to do the slightest work to investigate the validity of your own unsupported claims. I won't be bothering, again.

At least you managed to avoid blaming Debian or women for any of this...

Moderation

Time Reason Points Voter
2015-09-10 09:05 Informative +1 pete@pipedot.org

Junk Status

Not marked as junk