All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Ivanov <qmastery16@gmail.com>
To: linuxgpletc@redchan.it
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: GRSec is vital to Linux security
Date: Wed, 23 Jan 2019 23:46:55 +0300	[thread overview]
Message-ID: <CAAaskFDMjUzonLeHPmiy_VcB=jvQfF9giEaWcmNLKHDTqQt4BA@mail.gmail.com> (raw)
In-Reply-To: <fe8a4e103943d671ff0ce2c4f09609f9@redchan.it>

Interesting point of view. Well, to be honest it seems to me that
Linux kernel sacrifices the security for the sake of progress, so it
is quite bloated at the moment and I am not sure that even GRSecurity
could fix it. 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.

ср, 23 янв. 2019 г. в 21:22, <linuxgpletc@redchan.it>:
>
> There are two iron laws when it comes to the linux-kernel and it's
> facing towards the larger world.
>
> 1) The grsecurity-pax patch is absolutely vital if one wishes to not be
> hacked by chinese(TM). (And has been vital for the last 15+ years.)
>
> 2) GRSecurity is _blatantly_ violating the GPL by adding additional
> restrictive terms.
>
>
> Other things we have come to know is that
> A) Linus is a poor judge of quality, or just out of touch.
>
> To say that GRSecurity is garbage?
> No linus, it's just the layer covering up the shit heap that the
> linux-kernel is when it comes to exploitable code.
> That stench you smell is not that nice grassy cover over the garbage
> tip, it is what is below, what that top is holding down.
>
> You know... I would expect the things that Linus said about GRSecurity
> from a white woman... I would expect that. Knowing nothing, spouting
> bullshit, destroying lives. That's their _thing_.
>
> But from a man?
>
> Well, goes to show you. White men ain't men. Best they are is 40 year
> old bois. Faggots to say for short in American parlance.
>
> Same reason they won't hold it down when a bunch of fucking cunts CoC
> them. You build the whole edifice, then you let a bunch of do-nothing
> white women rule over the thing you built and you.
>
> But hey, that's Linux!

  reply	other threads:[~2019-01-23 20:47 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 [this message]
2019-01-23 22:28   ` linuxgpletc
2019-01-24 15:31   ` Enrico Weigelt, metux IT consult
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='CAAaskFDMjUzonLeHPmiy_VcB=jvQfF9giEaWcmNLKHDTqQt4BA@mail.gmail.com' \
    --to=qmastery16@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxgpletc@redchan.it \
    /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.