public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Questions about cfg80211's cfg80211_connect_params->crypto settings
Date: Mon, 26 Oct 2009 10:22:29 +0100	[thread overview]
Message-ID: <1256548953.28230.19.camel@johannes.local> (raw)
In-Reply-To: <200910260947.48365.hs4233@mail.mn-solutions.de>

[-- Attachment #1: Type: text/plain, Size: 778 bytes --]

On Mon, 2009-10-26 at 09:47 +0100, Holger Schurig wrote:

> I'm a but confused about what fields in "struct 
> cfg80211_connect_params" (now abbreviated as sme->)
> are relevant for me.
> 
> 
> sme->private
> ------------

I think you mean "privacy". I'm not sure about it right now, would have
to dig, but maybe the answer to the others helps you?

> sme->crypto.wpa_versions

> sme->crypto.n_ciphers_pairwise, sme->crypto.ciphers_pairwise

> sme->crypto.n_akm_suites, sme->crypto.akm_suites

All these pretty much exist for hw that doesn't want to use the IE(s)
contained in the connect parameters. If you send an assoc request with
those IEs, you can safely ignore the parameters here. It's just there so
one doesn't have to parse the IEs.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2009-10-26  9:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26  8:47 Questions about cfg80211's cfg80211_connect_params->crypto settings Holger Schurig
2009-10-26  9:22 ` Johannes Berg [this message]
2009-10-26 12:11   ` Holger Schurig
2009-10-26 12:22     ` Johannes Berg
2009-10-26 12:59       ` Holger Schurig
2009-10-26 13:03         ` Johannes Berg
2009-10-26 19:57 ` Dan Williams

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=1256548953.28230.19.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=linux-wireless@vger.kernel.org \
    /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