From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753158AbdFOPRN (ORCPT ); Thu, 15 Jun 2017 11:17:13 -0400 Received: from cock.li ([185.100.85.212]:59298 "EHLO cock.li" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752170AbdFOPRM (ORCPT ); Thu, 15 Jun 2017 11:17:12 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 15 Jun 2017 15:17:09 +0000 From: aconcernedfossdev@airmail.cc To: linux-kernel@vger.kernel.org Subject: The copyright to the linux kernel is being violated by GRSecurity, why is this OK? Message-ID: <8fd283defd08c0b71da8bb35553bb19c@airmail.cc> User-Agent: Roundcube Webmail/1.2.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The license grant the Linux Kernel is distributed under disallows the imposition of additional terms. The making of an understanding that the derivative work must not be redistributed (lest there be retaliation) is the imposition of an additional term. The communication of this threat is the moment that GRSecurity violates the license grant. Thence-forth modification, making of derivative works, and distribution of such is a violation of the Copyright statute. The concoction of the transparent scheme shows that it is a willful violation, one taken in full knowledge by GRSecurity of the intention of the original grantor. (Note: last month the GRSecurity Team removed the public testing patch, they prevent the distribution of the patch by paying customers by a threat of no further business: they have concocted a transparent scheme to make sure the intention of the Linux rights-holders (thousands of entities) are defeated) (This is unlike RedHat who do distribute their patches in the form the rights-holders prefer: source code, RedHat does not attempt to stymie the redistribution of their derivative works, GRSecurity does.).