public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: "PaX Team" <pageexec@freemail.hu>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] RIP hardened-sources
Date: Sat, 29 Apr 2017 15:46:54 +0200	[thread overview]
Message-ID: <5904994E.14957.457CA97@pageexec.freemail.hu> (raw)
In-Reply-To: <20170429131149.GQ28917@home.power>

On 29 Apr 2017 at 16:11, Alex Efros wrote:

> Hi!
> 
> On Sat, Apr 29, 2017 at 01:49:20PM +0200, Luis Ressel wrote:
> > in case anyone hasn't read in on LWN yet, here's what I'm talking
> > about: https://grsecurity.net/passing_the_baton.php
> 
> Sorry for OT, but is this legal? Or, more correct, is this will works?
> 
> Sure, they can sell their patch to Linux kernel without opensourcing that
> patch.

granted that 'open source' is a rather loaded term these days, i think it
never meant 'available to the public' (shareware would be 'open source' too
then), just that the license is 'open' (whose definition the FSF and others
don't necessarily agree on either). there's plenty of 'open source' licenced
code that never sees the light of day outside of a group of users.

> But at soon as their customers (say, some government org or large
> company) will APPLY that patch to Linux kernel and try to DISTRIBUTE that
> kernel on their computers

there's no need to speculate on this, the FSF has already answered it:
https://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.en.html#InternalDistribution



  reply	other threads:[~2017-04-29 13:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-29 11:49 [gentoo-hardened] RIP hardened-sources Luis Ressel
2017-04-29 12:47 ` Alex Efros
2017-04-29 15:56   ` Daniel Cegiełka
2017-04-29 16:52     ` Javier Juan Martinez Cabezon
2017-04-29 16:58       ` Luis Ressel
2017-04-30  8:15         ` Javier Juan Martinez Cabezon
2017-04-29 17:04     ` Luis Ressel
2017-04-29 18:43       ` Daniel Cegiełka
2017-04-29 20:34         ` "Tóth Attila"
2017-04-29 22:04           ` Brant Williams
2017-04-30 13:00           ` Andrew Savchenko
2017-04-30 13:16             ` Alex Efros
2017-04-30 14:34               ` Andrew Savchenko
2017-04-30 14:56                 ` "Tóth Attila"
2017-04-30 13:07   ` Andrew Savchenko
2017-04-29 13:11 ` Alex Efros
2017-04-29 13:46   ` PaX Team [this message]
2017-04-29 16:46     ` Alex Efros
2017-04-30 11:08       ` Alex Efros
2017-04-30 11:50         ` SK
2017-04-30 11:55           ` SK
2017-04-30 12:32             ` Andrew Savchenko
2017-04-30 12:56             ` Alex Efros
2017-04-30 13:28               ` Andrew Savchenko
2017-04-30 13:07           ` Daniel Cegiełka
2017-04-29 15:30   ` Paweł Hajdan, Jr.

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=5904994E.14957.457CA97@pageexec.freemail.hu \
    --to=pageexec@freemail.hu \
    --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