All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Micay <danielmicay@gmail.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening]
Date: Tue, 17 Nov 2015 02:41:38 -0500	[thread overview]
Message-ID: <564ADA32.5040708@gmail.com> (raw)
In-Reply-To: <CAFLxGvyUdURf8TkVOmzG0wraoGRUtLJH1+KsZUi8TJ-a4D9n4A@mail.gmail.com>

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

On 16/11/15 07:13 AM, Richard Weinberger wrote:
> On Mon, Nov 16, 2015 at 6:33 AM, Daniel Micay <danielmicay@gmail.com> wrote:
>> On 15/11/15 03:59 PM, Richard Weinberger wrote:
>>> On Fri, Nov 13, 2015 at 4:43 PM, west suhanic <west.suhanic@gmail.com> wrote:
>>>> Hello All:
>>>>
>>>> I am a hardened gentoo user. How can we get the grsecurity code into the
>>>> kernel?
>>>
>>> As soon all downsides and drawbacks are identified/resolved.
>>> Which basically means that we have to redo a lot (it not all).
>>
>> You might not be familiar with the grsecurity/PaX features and their
>> implementations but lots of people are. It's not unexplored territory
>> without known trade-offs. It has active developers who are happy to
>> answer questions about it (within reason).
> 
> I'll kindly ignore this personal attack.

I didn't mean this as a personal attack. I just found that statement to
be off i.e. it seems to imply that PaX/grsecurity are low quality and
that they need to be improved to upstream them, when IMO what really
needs to happen to just making the features more politically acceptable
even if it ends up making them harder to implement / less useful.


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

  reply	other threads:[~2015-11-17  7:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 15:43 [kernel-hardening] west suhanic
2015-11-13 22:23 ` [kernel-hardening] Valdis.Kletnieks
2015-11-13 23:21   ` [kernel-hardening] David Windsor
2015-11-15 20:59 ` [kernel-hardening] Richard Weinberger
2015-11-16  5:33   ` [kernel-hardening] Daniel Micay
2015-11-16  5:45     ` [kernel-hardening] Daniel Micay
2015-11-16  6:38       ` [kernel-hardening] David Windsor
2015-11-16 22:03         ` [kernel-hardening] Daniel Micay
2015-11-16 23:20           ` [kernel-hardening] Kees Cook
2015-11-16 23:17         ` [kernel-hardening] Kees Cook
2015-11-16 12:13     ` [kernel-hardening] Richard Weinberger
2015-11-17  7:41       ` Daniel Micay [this message]
2015-11-17 10:32         ` [kernel-hardening] Richard Weinberger
2015-11-16 23:14     ` [kernel-hardening] Kees Cook
2015-11-17  8:09       ` [kernel-hardening] Daniel Micay
2015-11-17 17:30         ` [kernel-hardening] 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=564ADA32.5040708@gmail.com \
    --to=danielmicay@gmail.com \
    --cc=kernel-hardening@lists.openwall.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.