All of lore.kernel.org
 help / color / mirror / Atom feed
From: linuxgpletc@redchan.it
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
Cc: Ivan Ivanov <qmastery16@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	gentoo-user@lists.gentoo.org, freebsd-chat@freebsd.org,
	misc@openbsd.org, rms@gnu.org
Subject: Fwd: Re: GRSec is vital to Linux security
Date: Thu, 24 Jan 2019 16:40:37 +0000	[thread overview]
Message-ID: <fefdf0dc5d84105b5877b135a822a52a@redchan.it> (raw)
In-Reply-To: <3efc6268-747d-0841-4249-5804fa9095ca@metux.net>


-------- Original Message --------
Subject: Re: GRSec is vital to Linux security
Date: 2019-01-24 16:25
 From: Boris Lukashev <blukashev@sempervictus.com>
To: linuxgpletc@redchan.it

You've never heard of VMware, I take it? Its a proprietary half Linux
which beats GPL suits with strong arm tactics and technicalities. Unlike
grsec, they don't distribute any source, because it's proof of theft...
Grsecs back port work is also public, since they're public upstream
patches or mailing list patches, the GCC plugins are the real magic...
Those aren't as GPL as the kernel, rap is patented, respectre likely
will be as well. The critical code changes they need (per CPU PGD, for
one) will not be accepted as Linus has "said so." Those code bits are
out there...

Also, doesn't matter if their patch leaks for the most part (4.4 just
did get leaked a few weeks back), as I wrote before, nobody really has
the time or skill available to maintain at their level of quality...
Linux might be free, but it's not something that should be run in
production when there's data or resource at stake.

Is the thought process that they should open up their commercial stable
code for free to all? Because RHEL has the same "don't leak" policy on
RHEL sources too... VMware even goes so far as to blatantly claim not to
use Linux. How about Google's internal Linux?

GPL is dead (has been for 20y), build the strongest defenses you can
with whatever code you can get and prove, because your adversaries won't
care about which license clause their tooling adheres to.

Boris Lukashev
Systems Architect
Semper Victus

-------- Original Message --------
 From: linuxgpletc@redchan.it
Sent: Wednesday, January 23, 2019 05:35 PM
To: bruce@perens.com
Subject: Re: GRSec is vital to Linux security
CC:
moglen@columbia.edu,bkuhn@sfconservancy.org,compliance@sfconservancy.org,blukashev@sempervictus.com,tcallawa@redhat.com,torvalds@osdl.org

  parent reply	other threads:[~2019-01-24 16:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 18:19 GRSec is vital to Linux security linuxgpletc
2019-01-23 20:46 ` Ivan Ivanov
2019-01-23 22:28   ` linuxgpletc
2019-01-24 15:31   ` Enrico Weigelt, metux IT consult
2019-01-24 16:03     ` Adam Borowski
2019-01-24 16:22     ` linuxgpletc
2019-01-24 16:31     ` GRSec is vital to Linux security -- SFConservancy = legal malpractice. Use own lawyer linuxgpletc
2019-01-24 16:40     ` linuxgpletc [this message]
2019-01-28 20:20   ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission linuxgpletc
2019-01-29  8:51   ` linuxgpletc
2019-01-29  9:10   ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission. (update) linuxgpletc
2019-01-29  9:38   ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission. (update 3) linuxgpletc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fefdf0dc5d84105b5877b135a822a52a@redchan.it \
    --to=linuxgpletc@redchan.it \
    --cc=freebsd-chat@freebsd.org \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@metux.net \
    --cc=misc@openbsd.org \
    --cc=qmastery16@gmail.com \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.