From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Ivan Ivanov <qmastery16@gmail.com>, linuxgpletc@redchan.it
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: GRSec is vital to Linux security
Date: Thu, 24 Jan 2019 16:31:10 +0100 [thread overview]
Message-ID: <3efc6268-747d-0841-4249-5804fa9095ca@metux.net> (raw)
In-Reply-To: <CAAaskFDMjUzonLeHPmiy_VcB=jvQfF9giEaWcmNLKHDTqQt4BA@mail.gmail.com>
On 23.01.19 21:46, Ivan Ivanov wrote:
> Linux really needs to stop adding new features and
> refactor itself to a smaller and more secure codebase before going
> forward. Maybe 1 year break would be nice.
Do you have some actual proposals / patches ?
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2019-01-24 15:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 18:19 GRSec is vital to Linux security linuxgpletc
2019-01-23 20:46 ` Ivan Ivanov
2019-01-23 22:28 ` linuxgpletc
2019-01-24 15:31 ` Enrico Weigelt, metux IT consult [this message]
2019-01-24 16:03 ` Adam Borowski
2019-01-24 16:22 ` linuxgpletc
2019-01-24 16:31 ` GRSec is vital to Linux security -- SFConservancy = legal malpractice. Use own lawyer linuxgpletc
2019-01-24 16:40 ` Fwd: Re: GRSec is vital to Linux security linuxgpletc
2019-01-28 20:20 ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission linuxgpletc
2019-01-29 8:51 ` linuxgpletc
2019-01-29 9:10 ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission. (update) linuxgpletc
2019-01-29 9:38 ` Author of GPC-Slots2 promises to sue "John Doe" who violated GPL recission. (update 3) linuxgpletc
2019-01-24 16:53 GRSec is vital to Linux security linuxgpletc
2019-01-24 20:18 ` Boris Lukashev
2019-01-25 16:34 ` linuxgpletc
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=3efc6268-747d-0841-4249-5804fa9095ca@metux.net \
--to=lkml@metux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxgpletc@redchan.it \
--cc=qmastery16@gmail.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.