From: Rik van Riel <riel@redhat.com>
To: intrigeri <intrigeri@boum.org>, kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] Patch for random mac address
Date: Thu, 25 May 2017 11:07:52 -0400 [thread overview]
Message-ID: <1495724872.20270.46.camel@redhat.com> (raw)
In-Reply-To: <85inkpie9o.fsf@boum.org>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
On Thu, 2017-05-25 at 09:31 +0200, intrigeri wrote:
> Hi,
>
> HacKurx:
> > Because this would be useful for distributions like Tails, Subgraph
> > OS, Kali Linux and other ...
>
> For what it's worth, it's unlikely that Tails ever uses this unless
> it
> can be controlled at runtime from userspace: we need to give users an
> option to disable MAC address randomization, because it breaks
> network
> connectivity in some cases.
That suggests maybe this kind of functionality should
be implemented in userspace, instead?
Maybe in NetworkManager, or whatever Tails uses to
manage the network. After all, setting the MAC address
to something else is already supported by the kernel...
--
All rights reversed
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2017-05-25 15:07 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 [this message]
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
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=1495724872.20270.46.camel@redhat.com \
--to=riel@redhat.com \
--cc=intrigeri@boum.org \
--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.