linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Joerg <pommnitz@yahoo.com>, linux-wireless@vger.kernel.org
Subject: Re: iw and non-ASCII SSIDs
Date: Fri, 26 Jun 2015 10:50:46 +0200	[thread overview]
Message-ID: <1435308646.2106.4.camel@sipsolutions.net> (raw)
In-Reply-To: <loom.20150625T224327-49@post.gmane.org> (sfid-20150625_225037_608129_0D468D05)

On Thu, 2015-06-25 at 20:50 +0000, Joerg wrote:
> Johannes Berg <johannes@...> writes:
> 
> > 
> > On Thu, 2015-06-25 at 16:12 +0000, Joerg wrote:
> > > Hello all,
> > > is there a way to submit a non-ASCII SSID with iw? One that 
> > > contains 
> > > 0 as in an octet with value zero?
> > 
> > No, that doesn't seem to be possible in the code.
> > 
> > But it's certainly possible in wp_supplicant config file, which you
> > should probably be using anyway?
> > 
> > johannes
> 
> That's what I thought from looking at the code, too. 
> 
> And no, this is for an IBSS network that uses an IPsec overlay for 
> security. 
> It doesn't use wpa_supplicant and changing the code that way would be 
> a major 
> hassle. 
> 
> I would volunteer to change iw to accept a hex encoded binary blob as 
> SSID. 
> What commandline would be acceptable?

Well I guess you're not interested in "connect" but rather "ibss join"
then.

We *could* break backward compatibility and say that if you pass "\x00"
it's no longer interpreted as the bytes 5c 78 30 30 but rather as the
byte 00, but I'm not sure we should?

OTOH, what choice do we really have - the only other option would be to
add a command line flag indicating that this behaviour is desired?

johannes

  reply	other threads:[~2015-06-26  8:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 16:12 iw and non-ASCII SSIDs Joerg
2015-06-25 18:10 ` Johannes Berg
2015-06-25 20:50   ` Joerg
2015-06-26  8:50     ` Johannes Berg [this message]
2015-06-26 11:27       ` Antonio Quartulli
     [not found]       ` <298558322.1785659.1435565847951.JavaMail.yahoo@mail.yahoo.com>
2015-06-29  8:23         ` Johannes Berg
2015-06-29 16:58           ` Paul Stewart

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=1435308646.2106.4.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pommnitz@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).