From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5E557CA9EB5 for ; Mon, 4 Nov 2019 17:58:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 37A5020B7C for ; Mon, 4 Nov 2019 17:58:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=firemail.cc header.i=@firemail.cc header.b="nQEfvGEP" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729514AbfKDR6e (ORCPT ); Mon, 4 Nov 2019 12:58:34 -0500 Received: from mx1.cock.li ([185.10.68.5]:36239 "EHLO cock.li" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728392AbfKDR6d (ORCPT ); Mon, 4 Nov 2019 12:58:33 -0500 MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=firemail.cc; s=mail; t=1572890311; bh=20O1UwoUgfY4uPo310rCxHNPlUK3x5F0/7K9qaCdM68=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=nQEfvGEP06nrP9k7AEpDErTnj18zH17QZzU4B//ae1SAmoCZXKZS8ZmKaklbMQO5n ll0dHb+WI4wkIRuP3Xck05fpvaWFiznw21TSkK0XVegLyFSFGuxk8kQGdzzghsZkwD 44IJviXEQOVifPrK/ZnJGqMWRw4mjyNVC3F+scokgYKsRdEgfNqM8RBweCGkoeSBUz U5TeEBAUIBgMgqiSed3Glc3Ua54CvLO5Q7fqR2rjhVoCQNu4bFVmE6mv/VQpimrzs9 fGYswoD3d95azWPvUh23qMkYnhlzDY3I5ofGRDN8dJcaUy1SjJpX/Sdn9I3xTgPtvX 59cPicojy0u1Q== Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 04 Nov 2019 17:58:30 +0000 From: nipponmail@firemail.cc To: linux-kernel@vger.kernel.org Cc: ruben@mrbrklyn.com, mrbrklyn@panix.com Subject: Re: Will no-one sue GrSecurity for their blatant GPL violation (of GCC and the linux kernel)? - BP and EFF have addressed In-Reply-To: References: Message-ID: <06a4c535e89a1485307fd7e93f18b4d3@firemail.cc> X-Sender: nipponmail@firemail.cc User-Agent: Roundcube Webmail/1.3.6 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Bruce Perens and the EFF have addressed this, it is indeed a violation to add an additional restrictive term such as that: they are threatening a penalty, using a negative covenant, if the customer utilizes the permissions granted to him (and GrSecurity) by the Copyright holder of the original Work. GrSecurity does not have an independent legal right to create non-separable derivative works _at_all_, they only have permission to do so IF abiding by the terms the Copyright holder set regarding HIS Work: which are NO additional restrictive terms. Here GrSecurity HAS added an additional restrictive term: NO free redistribution of the derivative work: and they enforce this via penalty: perens.com/2017/06/28/warning-grsecurity-potential-contributory-infringement-risk-for-customers/ Page 10 onward has discussion on the copyright issue aswell: perens.com/static/OSS_Spenger_v_Perens/0_2018cv15189/docs1/pdf/18.pdf (And yes, IAAL) On 2019-11-04 17:36, ams@gnu.org wrote: > One is not under obligation to guarantee that new versions are > distributed to someone, which also means obligations can be terminated > for any reason. So while grsecurity might not be doing the morally > and ethically right thing, I do not think they are violating the GNU > GPL. You're still free to redistribute the patches, but grsecurity > isn't under obligation to give you future updates. > > Their agreement text is located at > https://grsecurity.net/agree/agreement_faq