From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Safety in Kernel Development
Date: Tue, 18 Aug 2015 11:46:31 -0400 [thread overview]
Message-ID: <4032.1439912791@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 18 Aug 2015 21:58:15 +0800." <CAD-N9QVC69sjt=JV-v9ZdMg6FLk_9BgL=ep3NatksPLyT94C1w@mail.gmail.com>
On Tue, 18 Aug 2015 21:58:15 +0800, ????????? said:
> Since I knew that Linux kernel didn't accept the pax/grsecurity , but wrote
> its own implement, and some linux developers do not have sense of security,
> I think linux security will be a problem in the future.
The fact that a specific security patch that is very invasive and comes with
some large tradeoffs was never submitted in a form suitable for merging is
*not* the same thing as kernel developers not having a sense of security.
Note that large sections of what used to be in the grsecurity patch *have*
been reworked, submitted, and accepted into the kernel.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150818/08abba6f/attachment.bin
next prev parent reply other threads:[~2015-08-18 15:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 13:25 Safety in Kernel Development Kenneth Adam Miller
2015-08-18 13:40 ` Robert P. J. Day
2015-08-18 13:45 ` Kenneth Adam Miller
2015-08-18 13:58 ` 慕冬亮
2015-08-18 15:25 ` Greg KH
2015-08-18 15:46 ` Valdis.Kletnieks at vt.edu [this message]
2015-08-18 14:01 ` leo kirotawa
2015-08-18 14:03 ` Kenneth Adam Miller
2015-08-18 22:22 ` Ruben Safir
2015-08-18 15:01 ` Victor Rodriguez
2015-08-18 15:03 ` Kenneth Adam Miller
2015-08-18 13:52 ` Victor Rodriguez
2015-08-18 14:01 ` Kenneth Adam Miller
2015-08-18 22:27 ` Ruben Safir
2015-08-19 0:30 ` Kenneth Adam Miller
2015-08-19 7:22 ` Ruben Safir
2015-08-19 7:23 ` Ruben Safir
2015-08-19 13:20 ` Kenneth Adam Miller
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=4032.1439912791@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).