public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Is this Grsecurity patch issue going to harm IPFire going forward?
Date: Fri, 28 Aug 2015 12:29:12 +0100	[thread overview]
Message-ID: <1440761352.18358.65.camel@ipfire.org> (raw)
In-Reply-To: <55DF5A25.7000607@gmail.com>

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

Hi,

the short answer is: Probably not.

The long answer is: Yes, it will certainly have an impact on the
security of many Linux-based systems. IPFire is only one of them.

The technical issue for us will be that kernel updates won't be as easy
for us since we will need to make work that is usually done in the
grsecurity project. Frankly we do not have the expertise for that. Even
if we had we would have the time and it won't make sense to do the same
work multiple times.

I find that this is a great loss for the free software world. If all
free software projects see themselves forced to remove their code from
"the market" there would not be much left. We all fight the same issues
here, since our software is used by companies which make lots of money
out of it and do development work based on IPFire but do not give
anything back.

The grsecurity case is a very severe case though.

Sure it is free software in the end and we all wouldn't do free
software if we didn't know this from the beginning. We do not expect
money from every single user, because other things are even more
important. But at the end of the day money is needed to run the
project. If someone is paying that from their own pocket and an other
one is making the huge profit, something is *clearly* wrong.

Therefore I can personally understand Brad and the PaX team very well
and I understand that they see this is a threat to their name and
future work.

So we dearly *hope* that this entire dispute can be settled and Brad is
not forced to make the stable patches only available for the "sponsors"
which are paying customers then. This will be a huge loss for IPFire
and all its users as well as many other projects that rely on
grsecurity.

Hope this answers your question.

Best,
-Michael

On Thu, 2015-08-27 at 14:42 -0400, William Pechter wrote:
>       Important Notice Regarding Public Availability of Stable
> Patches
>       <https://www.grsecurity.net/index.php#>
> 
> Due to continued violations by several companies in the embedded
> industry of grsecurity^® 's trademark and registered copyrights,
> effective September 9th 2015 stable patches of grsecurity will be
> permanently unavailable to the general public. *For more information,
> read the full announcement. <https://www.grsecurity.net/announce.php>
> 
> https://www.grsecurity.net/announce.php
> *
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-08-28 11:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 18:42 William Pechter
2015-08-28 11:29 ` Michael Tremer [this message]
2015-08-28 14:46   ` William Pechter
2015-08-28 16:15     ` Michael Tremer
2015-08-28 16:32     ` Paul Simmons
2015-08-28 16:34       ` William Pechter
2015-08-28 17:04         ` Larsen
2015-08-28 18:53           ` Michael Tremer
2015-08-28 18:49       ` Michael Tremer
     [not found] <1441059261.18358.130.camel@ipfire.org>
2015-09-09 16:35 ` IT Superhack
2015-09-11 14:53   ` Michael Tremer

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=1440761352.18358.65.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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