From: Greg KH <gregkh@linuxfoundation.org>
To: Shawn <citypw@gmail.com>
Cc: "Kees Cook" <keescook@chromium.org>,
"Rik van Riel" <riel@redhat.com>,
"Mathias Krause" <minipli@googlemail.com>,
"Daniel Cegiełka" <daniel.cegielka@gmail.com>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: Re: [kernel-hardening] It looks like there will be no more public versions of PaX and Grsec.
Date: Thu, 4 May 2017 09:03:56 -0700 [thread overview]
Message-ID: <20170504160356.GA16988@kroah.com> (raw)
In-Reply-To: <CABniQZNYUzDTiEnd5AzJ6rJ=VPvT_ph0RK38sPS+u=BjXVQ+Jw@mail.gmail.com>
On Thu, May 04, 2017 at 10:11:04PM +0800, Shawn wrote:
> That announcement only represented the POV from a group of ppl. From
> my( and other ppl from HardenedLinux) perspective, Linux foundation is
> a commercial company and very good at PR but zero integrity to us.
A slight correction here please. The LF is a non-profit organization[1]
set up to promote Linux and allow companies who want to see Linux
succeed, get together and do this. The LF happens to sponsor a few
kernel developers (me and Linus), but they can not tell us what to do at
all.
They also are a place that companies have come together to help with the
state of security in the Linux and Open Source ecosystem, starting CII
which offers grants to anyone who wants to get paid to do security work
(new features, support, audits, etc.) CII doesn't make any money, it
gives money away! Of course it does press releases saying what projects
it funds in order to get other projects and people to submit project
proposals to continue this work. I know of at least 2 new kernel
security projects that recently got funding because of this.
So there is no "integrity" that the LF can, or can not, have when it
comes to anyone here as the LF doesn't actually _do_ anything when it
comes to kernel development (again, other than funding 2 developers
directly).
> They don't respect individuals and the community.
That's a load of crap, really. The LF has always had a kernel community
developer as a full board member, and sponsors conferences, travel
funding, hardware acquisition, intern programs, and lots of other stuff.
I don't know of any kernel community request that the LF has _not_
funded, do you?
The LF is all about making the whole community work well together, and
that includes both individual developers and companies as this is a
symbiotic relationship (companies use Linux, fund its development,
create new hardware for Linux to run on, etc.) Without one part of the
group, Linux would not succeed at all, and they know that quite well.
If the LF didn't "individuals and the community", I know I wouldn't be
working for them.
So I don't know why anyone would be "upset" at the LF here, all they
have done is actually fund people to do kernel security work, including
members of the grsecurity team! How is doing that somehow "bad"? Do
you want to go back to 2+ years ago when they were not doing this
funding at all?
And does no one remember how things were before there was a LF? Do you
really want to go back to those days? Were they somehow better than
things are now? As someone who remembers those times quite well, I can
assure you that they were not.
Sorry for the digression,
greg k-h
[1] Yes, it's structured as a trade organization, it has to be that way
from a legal point of view in order for companies to be able to
help Linux and work together. Without it, companies would be
violating anti-trust laws and would not be able to help the
community out at all. Think of the LF as the "Milk Advisory Board"
for Linux.
next prev parent reply other threads:[~2017-05-04 16:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 21:05 [kernel-hardening] It looks like there will be no more public versions of PaX and Grsec Daniel Cegiełka
2017-04-26 22:04 ` Kees Cook
2017-05-01 22:01 ` Mathias Krause
2017-05-02 0:09 ` Rik van Riel
2017-05-02 14:46 ` Shawn
2017-05-02 18:55 ` Kees Cook
2017-05-03 4:50 ` Shawn
2017-05-03 18:56 ` Rik van Riel
2017-05-03 19:36 ` Daniel Micay
2017-05-04 5:45 ` Kees Cook
2017-05-04 6:47 ` Lionel Debroux
2017-05-05 19:54 ` Kees Cook
2017-05-04 14:11 ` Shawn
2017-05-04 16:03 ` Greg KH [this message]
2017-05-04 17:12 ` Shawn
2017-05-04 17:23 ` Greg KH
2017-05-02 21:16 ` Mathias Krause
2017-05-02 21:50 ` Casey Schaufler
2017-05-02 22:57 ` Kees Cook
2017-05-03 19:02 ` Rik van Riel
2017-05-03 19:27 ` Daniel Micay
2017-05-02 0:39 ` Olof Johansson
2017-05-02 0:44 ` Casey Schaufler
2017-05-02 0:54 ` Kees Cook
2017-05-11 1:24 ` PaX Team
2017-05-11 16:30 ` Daniel Micay
2017-05-11 18:02 ` Kees Cook
2017-05-12 11:34 ` Hunger
2017-07-31 13:38 ` Solar Designer
2017-05-02 11:11 ` David Gens
2017-05-02 21:27 ` Mathias Krause
2017-05-03 8:59 ` David Gens
2017-05-03 19:10 ` Rik van Riel
[not found] <1788778362.1495506.1493751985632.ref@mail.yahoo.com>
2017-05-02 19:06 ` Lionel Debroux
2017-05-02 22:35 ` Kees Cook
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=20170504160356.GA16988@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=citypw@gmail.com \
--cc=daniel.cegielka@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=minipli@googlemail.com \
--cc=riel@redhat.com \
/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.