public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Schiffbauer <mschiff@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] The state of grsecurity in gentoo
Date: Fri, 4 Sep 2015 14:37:37 +0200	[thread overview]
Message-ID: <20150904123737.GC14064@schiffbauer.net> (raw)
In-Reply-To: <d29b64b9d11193e4a5d0caaf70ab3a0c@posteo.de>

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

* philipp.ammann@posteo.de schrieb am 04.09.15 um 13:33 Uhr:
> Am 03.09.2015 23:08 schrieb Marc Schiffbauer:
> > True and what I wanted to say with the OTOH part. But doesn't this 
> > apply
> > to any sponsor? I mean we are talking about GPL'ed Software... does the
> > GPL permit to distribute source under some kind of NDA?
> > 
> > I fully respect their decision but I hope things will be back to normal
> > again soon.
> > 
> 
> No you can't override the GPL with an NDA. But a sponsor - who is 
> selling products based on grsecurity - is not required to make the code 
> available to the general public, only to the customer who pays for the 
> product. They're also not required to make their /patches/ available, 
> only the complete source. So even if you get the sources from a customer 
> (or you buy the product yourself), you would have to diff the code 
> against a vanilla kernel - and then you only get a huge patch that 
> includes *all* changes. Extracting just the grsecurity patch from that 
> is complicated and error prone. You'll probably run into less bugs if 
> you just stick to the public testing patches.

Yes, but the point I was trying to make is: Such a customer can make the 
sources available to the public. I am NOT saying we should do this but 
in theory it would be possible.
Lets see what the future brings. This is going to be too OT ;)

-Marc

-- 
0x35A64134 - 8AAC 5F46 83B4 DB70 8317
             3723 296C 6CCA 35A6 4134

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-09-04 12:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 16:13 [gentoo-hardened] The state of grsecurity in gentoo Anthony G. Basile
2015-09-02 17:22 ` Aaron W. Swenson
2015-09-02 19:17 ` Francisco Blas Izquierdo Riera (klondike)
2015-09-03 19:28 ` Marc Schiffbauer
2015-09-03 19:46   ` Matthew Thode
2015-09-03 21:08     ` Marc Schiffbauer
2015-09-04 11:33       ` philipp.ammann
2015-09-04 12:37         ` Marc Schiffbauer [this message]
2015-09-04 20:12           ` Apple Apple
2015-09-04 21:23           ` Javier Juan Martínez Cabezón
2015-09-05  9:44 ` Marc Schiffbauer
2015-09-05 13:55   ` Anthony G. Basile
2015-09-18  8:53 ` J. Roeleveld

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=20150904123737.GC14064@schiffbauer.net \
    --to=mschiff@gentoo.org \
    --cc=gentoo-hardened@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox