All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Micay <danielmicay@gmail.com>
To: Anisse Astier <anisse@astier.eu>, Kees Cook <keescook@chromium.org>
Cc: HacKurx <hackurx@gmail.com>, Rik van Riel <riel@redhat.com>,
	intrigeri <intrigeri@boum.org>,
	"kernel-hardening@lists.openwall.com"
	<kernel-hardening@lists.openwall.com>
Subject: Re: [kernel-hardening] Patch for random mac address
Date: Fri, 26 May 2017 04:23:45 -0400	[thread overview]
Message-ID: <1495787025.2392.0.camel@gmail.com> (raw)
In-Reply-To: <20170525212839.GA21842@bifrost>

On Thu, 2017-05-25 at 23:28 +0200, Anisse Astier wrote:
> Hi,
> 
> On Thu, May 25, 2017 at 10:28:19AM -0700, Kees Cook wrote:
> > On Thu, May 25, 2017 at 8:59 AM, Rik van Riel <riel@redhat.com>
> > wrote:
> > > On Thu, 2017-05-25 at 17:47 +0200, intrigeri wrote:
> > > > Rik van Riel:
> > > > > That suggests maybe this kind of functionality should
> > > > > be implemented in userspace, instead?
> > > > > Maybe in NetworkManager, […]
> > > > 
> > > > It's already implemented in NetworkManager :)
> > > 
> > > So this kernel patch does not solve any problem,
> > > because the solution has already been implemented
> > > in userspace?
> > 
> > It makes sure you can never not randomize the MAC, no matter what
> > userspace is doing. I'm not opposed to the idea, but it feels like
> > overkill to me.
> > 
> > BTW, the proposed patch is slightly wrong: it still allows userspace
> > to change the MAC address. The ifdef with the return 0 should be
> > moved
> > up (and "return 0" seems like a bit of a lie: maybe -EINVAL or
> > -ENOTSUPPORTED?). How about sending a v2 with that fixed, inline,
> > etc.
> > And see if other people chime in?
> 
> Yes, the original grsec patch is slightly different.

It was never included in grsecurity, so it's not really a grsecurity
patch.

  reply	other threads:[~2017-05-26  8:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 20:44 [kernel-hardening] Patch for random mac address HacKurx
2017-05-24 22:40 ` Casey Schaufler
2017-05-24 23:05   ` Lukas Odzioba
2017-05-25  7:31 ` intrigeri
2017-05-25 15:07   ` Rik van Riel
2017-05-25 15:47     ` intrigeri
2017-05-25 15:59       ` Rik van Riel
2017-05-25 17:28         ` Kees Cook
2017-05-25 21:28           ` Anisse Astier
2017-05-26  8:23             ` Daniel Micay [this message]
2017-05-26  7:55           ` HacKurx
2017-05-26 12:34             ` Anisse Astier
2017-05-26 14:41               ` HacKurx
2017-06-09 12:00               ` HacKurx
2017-06-09 13:01                 ` Anisse Astier
2017-05-25 15:48   ` Theodore Ts'o
2017-06-09 13:11     ` Matt Brown
2017-06-10  7:00       ` HacKurx

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=1495787025.2392.0.camel@gmail.com \
    --to=danielmicay@gmail.com \
    --cc=anisse@astier.eu \
    --cc=hackurx@gmail.com \
    --cc=intrigeri@boum.org \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.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.