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=-5.8 required=3.0 tests=BAYES_00,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 DCDEBC433E0 for ; Sat, 2 Jan 2021 07:37:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A2DE722241 for ; Sat, 2 Jan 2021 07:37:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726499AbhABHhA (ORCPT ); Sat, 2 Jan 2021 02:37:00 -0500 Received: from mail.cock.li ([37.120.193.124]:39938 "EHLO mail.cock.li" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726080AbhABHhA (ORCPT ); Sat, 2 Jan 2021 02:37:00 -0500 MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=firemail.cc; s=mail; t=1609572970; bh=K7xFAmTyeXv3xrpa3PQqsooMReKn36uGXHQtqdECa6I=; h=Date:From:To:Cc:Subject:From; b=B+LK2Zp9cL8SR+5whuj6b4m0l2hyCmBgL5tbvV6BCWlUvzNmmXxRVqi0ozF0JTA8S Hr8DE415jj9J05NJBuSSKjAFazLMkgwj+eoTN4vbUDCsq/U+k1yh8NB7cEkOcxlhEk JUTAvEGp9ukCXe9HBqzTVJPINk3rPihlGl663LhHaUrGZBfaEiAj7S+fMUBX8wbD3d msEZ/8N6TmtuRqMPBfEoy94hA8fX0lCrgHt1abj8W+jTHjWs6oTVotkaOgdXEpifRD nHW2eq8bs+eOejmEP1PCLbMKviB4+38w7UtHRnq8jLjqec5hlNiks8NR28t8viY8ps E7ispAvdgAUwg== Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 02 Jan 2021 07:36:11 +0000 From: nipponmail@firemail.cc To: linux-kernel@vger.kernel.org Cc: rms@gnu.org, bruce@perens.com, esr@thyrsus.com, moglen@columbia.edu, blukashev@sempervictus.com, tcallawa@redhat.com, editor@lwn.net, skraw.ml@ithnet.com, torvalds@osdl.org Subject: Grsecurity GPL Violations: Linus/FSF/SFConservancy won't defend. Claw back your copyrights. BSD-in-Practice was not the deal. Message-ID: <47819d6850bd78c91601fbb9fb2a76f7@firemail.cc> X-Sender: nipponmail@firemail.cc User-Agent: Roundcube Webmail/1.3.15 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Silence is consent. > Are there FOSS developers making decent money via Patreon, GoFundMe, > whatever? Yes, Grsecurity is making good money. They simply added a no-redistribution agreement to their patch of the Linux Kernel. > ( > https://perens.com/2017/06/28/warning-grsecurity-potential-contributory-infringement-risk-for-customers/ > ) The FSF, Software Freedom Conservancy, and the Corporate Linux Kernel Developers all agree that this is fine (silence is consent). > https://twitter.com/spendergrsec/status/1293155787859206146 > Importantly, neither the FSF nor the SFC, nor in fact any actual lawyer > agrees with this bizarre claim from an anonymous troll. More info about > the source of the claim can be found here: > https://grsecurity.net/setting_the_record_straight_on_oss_v_perens_part1 > Thanks for doing your part, "Dr" to continue the troll's harrassment >> LOL. " #GRSecurity violates both the Linux kernel's copyright and the >> #GCC #copyright by forbidding redistribution of the patches (in their >> Access Agreement): which are non-seperable derivative works... Contributors should blanket-revoke their contributions from all free-takers since they didn't agree to BSD-in-Practice. They should also claw-back any transferred copyrights from the FSF using the 30 year clawback provision in the US Copyright Act. Design of how a program works is a copyrightable aspect (Ex: How RMS designed GCC 30 years ago or so etc) Had to repost this because the linux admins deleted the email: > https://lkml.org/lkml/2020/12/28/2518 > The message you requested cannot be found. > The message you requested cannot be found. The message with the url > http://feisty.lkml.org/lkml/2020/12/28/2518 does not exist in the > database. Grsecurity GPL Violations: Bring a CASE act claim every time GrSecurity releases a new infringing work? (GRSecurity blatantly violates the clause in the Linux kernel and GCC copyright licenses regarding adding addtional terms between the licensee of the kernel / gcc and furthur down-the-line licensees, regarding derivative works) (The linux kernel has 1000s of copyright holders) (All who shake at the knees at the thought of initiating a federal Copyright lawsuit)