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 19:49:10 +0100	[thread overview]
Message-ID: <1440787750.18358.94.camel@ipfire.org> (raw)
In-Reply-To: <1440779551.14090.7.camel@hughes.net>

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

On Fri, 2015-08-28 at 11:32 -0500, Paul Simmons wrote:
> On Fri, 2015-08-28 at 10:46 -0400, William Pechter wrote:
> > Michael Tremer wrote:
> > > 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.
> > Thank you for the in depth answer...
> > 
> > I hope there's someone out there who will leak the name of the
> > large
> > company so there's a change in their behavior and a loss of
> > at least a little of their customer base.
> > 
> > Unfortunately, there's big money in computer security these days
> > and
> > some large companies have been buying up the Open Source
> > products.  I remember when Cisco replaced their sensor box under
> > Solaris
> > (IIRC it was Solaris, not SCO) with a Linux customized box
> > with Snort...
> > 
> > Perhaps the Open Source community needs to pool resources in some
> > kind
> > of cooperative to keep these projects going.
> > 
> > At least Snort is still available after the Cisco buyout.  It could
> > have
> > been worse and been an Oracle purchase which usually causes a pull
> > of
> > the open source version from the net.
> > 
> > Bill
> > 
> 
> I was about to suggest a "grsecurity sponsorship funding drive" for
> IPFire, until I found that sponsorship costs $200USD/month.
> 
> https://grsecurity.net/sponsors.php
> 
> Crappola - I can't even come up with $10USD to send to IPFire, so I
> suppose that's a bad idea.  If I win a sweepstakes, I'll send the
> money :-).

I certainly like the idea to help funding the project. However I do not
see any point in raising money to give to the lawyers to defend the
trademark or to sue because of the GPL violation. That money could
certainly be used better than being given to the lawyers.

Just donate to the projects you use and love. Every single bit does
help. It will sum up soon.

-Michael

> 
> Paul

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

  parent reply	other threads:[~2015-08-28 18:49 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
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 [this message]
     [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=1440787750.18358.94.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