All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Joerg Pommnitz <pommnitz@yahoo.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iw and non-ASCII SSIDs
Date: Mon, 29 Jun 2015 10:23:36 +0200	[thread overview]
Message-ID: <1435566216.2156.11.camel@sipsolutions.net> (raw)
In-Reply-To: <298558322.1785659.1435565847951.JavaMail.yahoo@mail.yahoo.com>

[please don't use HTML]

On Mon, 2015-06-29 at 08:17 +0000, Joerg Pommnitz wrote:
> We don't have to break compatibility. The commandline syntax of iw is
> iw [options] command
> My suggestion would be a new option "--binary-ssid" that sets a flag 
> and causes all SSID to be treated as a hex encoded binary blob:
> iw --binary-ssid dev wlan0 ibss join 0034AA 2412
> and for consistency
> iw --binary-ssid dev wlan0 connect 0034AA
> 
> Alternatively the option could be "--escaped-ssid" that would 
> activate an escape processing for the SSID as you suggested. My 
> preference is "--binary-ssid", because I'm always a little bit unsure 
> what actually arrives in the program after the shell has done its own 
> escape processing.
> 


Yeah, that seems reasonable, though perhaps easier to do as

  iw dev wlan0 ibss join --binary-ssid 0034AA 2412

since options before the command are treated as generic iw options.

Then again, if all places that use an SSID were to use a
"parse_ssid(argv[7])" function then the former could also be
implemented.

johannes

  parent reply	other threads:[~2015-06-29  8:23 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
2015-06-26 11:27       ` Antonio Quartulli
     [not found]       ` <298558322.1785659.1435565847951.JavaMail.yahoo@mail.yahoo.com>
2015-06-29  8:23         ` Johannes Berg [this message]
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=1435566216.2156.11.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 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.