From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Questions about cfg80211's cfg80211_connect_params->crypto settings
Date: Mon, 26 Oct 2009 13:11:47 +0100 [thread overview]
Message-ID: <200910261311.47164.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <1256548953.28230.19.camel@johannes.local>
> > 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.
Okay, then I conclude that it's save to ignore
sme->privacy
sme->crypto.wpa_versions
sme->crypto.n_ciphers_pairwise
sme->crypto.ciphers_pairwise
sme->crypto.n_akm_suites
sme->crypto.akm_suites
inside .connect() if I check sme->crypto.cipher_suite for
WLAN_CIPHER_SUITE_WEP40
WLAN_CIPHER_SUITE_WEP104
WLAN_CIPHER_SUITE_TKIP
WLAN_CIPHER_SUITE_CCMP
0 (meaning no encryption/WEP obfuscation)
lbs_cfg_connect() calls lbs_associate() which hands the complete
sme->ie to as a TLV to the firmware. However, I don't do any
parsing of sme->ie by myself.
--
http://www.holgerschurig.de
next prev parent reply other threads:[~2009-10-26 12:12 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
2009-10-26 12:11 ` Holger Schurig [this message]
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=200910261311.47164.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=johannes@sipsolutions.net \
--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