All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Bob Copeland <me@bobcopeland.com>
Cc: Chun-Yeow Yeoh <yeohchunyeow@gmail.com>,
	devel@lists.open80211s.org, linux-wireless@vger.kernel.org,
	linville@tuxdriver.com
Subject: Re: [PATCH] {nl, cfg, mac}80211: Implement hidden mesh ID
Date: Mon, 08 Sep 2014 15:15:20 +0200	[thread overview]
Message-ID: <1410182120.7983.12.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20140908122454.GA29495@localhost> (sfid-20140908_142549_984867_17DF5DF0)

On Mon, 2014-09-08 at 08:24 -0400, Bob Copeland wrote:
> On Mon, Sep 08, 2014 at 02:01:22PM +0800, Chun-Yeow Yeoh via Devel wrote:
> > The hidden mesh ID is use to enhance the security of
> > open mesh and possible secured mesh later on by not
> > advertising the mesh ID during beacon generation,
> > similar to hidden SSID implemented in AP mode.
> 
> I'm unconvinced - hidden SSID is not much of a security feature and it
> seems like this would break all manner of things.  Is it really worth
> the pain when people can just use a secure mesh instead?

It's certainly not a security feature at all.

So why bother introducing the old hidden SSID mistake again in a new
protocol? It caused all kinds of pain there, and almost certainly will,
and there already are few implementations to interoperate with and this
is likely to not interoperate at all, right?

I really don't think we should allow this. If you need to hide the
network name then maybe just give it a random/useless name?

johannes


  parent reply	other threads:[~2014-09-08 13:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08  6:01 [PATCH] {nl, cfg, mac}80211: Implement hidden mesh ID Chun-Yeow Yeoh
2014-09-08 12:24 ` Bob Copeland
2014-09-08 12:35   ` Yeoh Chun-Yeow
2014-09-08 13:15   ` Johannes Berg [this message]
2014-09-09  2:06     ` Yeoh Chun-Yeow

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=1410182120.7983.12.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=devel@lists.open80211s.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=me@bobcopeland.com \
    --cc=yeohchunyeow@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.