[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology

Name
Options
Comment
Verification
4chan Pass users can bypass this verification. [Learn More] [Login]
File
  • Please read the Rules and FAQ before posting.
  • You may highlight syntax and preserve whitespace by using [code] tags.

08/21/20New boards added: /vrpg/, /vmg/, /vst/ and /vm/
05/04/17New trial board added: /bant/ - International/Random
10/04/16New board for 4chan Pass users: /vip/ - Very Important Posts
[Hide] [Show All]


[Advertise on 4chan]


File: erin_anmgrl.jpg (243 KB, 334x500)
243 KB
243 KB JPG
>>106509471
>GRsecurity isn't violating the GPL though. Nothing about the GPL requires you to give patches to anyone and everyone. They only require that you produce the source to anyone whom you yourself distribute the software to (and require them to do the same).

Yes they are.
Article 2 section 6 of the GPLv2 states that the distributor of a derivative work may not impose any furthur restrictions on the redistribution of the affected work.

Grsecurity adds a restriction: that if a person redistributes the derivative work: they lose money.

A court would understand what the GPL is about, and that GRsecurity is violating it.

>but at the same time they're not allowed to re-write the GPL
You're an idiot: and I'll kill you if I meet you:
The GPL is not protecting "itself" from being "rewritten" in Article 2 section 6.

It is govorning the relationship between the derivative-work distributor, and the distributee:
it says that the distributor of a derivative work may not impose hardships on the distributee beyond that which is in the text of the memorandum of the original work's license to the distributor.

It is not saying "u can't change the text of the GPL!". Copyright law allready does that. Grsecurity has no right to modify the FSF's license work-product called the GPL at all.

The GPL says that you can modify Linux; but if you frustrate the distributee's ability to do what you have done: then your license is canceled.

Which is what Grsecurity has done.

>(which is why they don't do that. Their business contract is a separate agreement)
That does not matter: the GPL governs that "seperate agreement": as it is pertaining to the corpus of the copywritten work: Linux (and GCC).

Grsecurity has no right to make contracts with other people, regarding it's derivative work of the Linus Kernel and GCC: the Copyright office says the original copyright holder _CONTROLS_ derivative works.

Not Grsecurity. Not down-the line programmers.
Again: I'll kill you straight dead.
>>
don't care. rewriting in rust with MIT licence. thanks for the code faggot
>>
>>106509549
>inferior product is less restrictive and companies will stop stealing mine
I'm fine with it.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.